Answer:- To achieve this, you will require to remove the JsonFormatter from the Register() section of the WebApiConfig.cs configuration file in the App_Start folder. Now to remove JsonFormatter, you need to include the following lines of code in the configuration file. config.Formatters.Remove(config.Formatters.JsonFormatter) With this, regardless of what was defined. Overriding the values from the accept header web will return the data in the JSON format only.

Answer:- 1. Client and Server Constraint – Specifies that the client will send a request to the server, and then the server will respond to that request. 2. Stateless Constraint – It specifies that the communication between the client and the server is encrypted. And no data of the client is stored anywhere on the server-side. 3. Cacheable Constraint – Cacheable constraint commands the server to send all the data in the cacheable form. So that client need not be required to request data for particular item data dozens of times. 4. Uniform Interface Constraint – This constraint expresses that the interface for the client, regardless of which device they are using, must give the similar and uniform interface 5. Layered System – It helps increase proficiency and reduces the functioning load by distributing the caches with each layer.

Answer:- It depends on the API provider. A few provide their services for free. And, a few may ask you to pay for using it boundlessly. But, the one providing it for free may bound you with some limitations in using their API services.

Answer:- A resource includes all the content on the web page. Including HTML pages, Images, Texts, Videos, and all the data present on it. One needs to request the server to get access to these resources. And, if the service provider approves the request, we get hold of all the content or resources.

Answer:- Payload is the data that an individual wants from the service provider. The HTTP body includes tons of other pieces of information in which the user may not be interested. So, here payload helps to distinguish between the required data and the unimportant data.

Answer:- 1. Omits firewall problems while using HTTP protocols. 2. Uses XML format for sending responses and status messages. 3. Independent and easy to use. 4. Ablest for transporting data in a decentralized environment.

Answer:- 1. Slower than other available services. 2. Support different programming languages that make it inconsistent with its performance. 3. Only one consumer can use the SOAP services at a time.

Answer:- It is the collection of customs obeyed to process and deploy data. It defines the syntaxes to be used, data flow, data type, and management of the administrator. A system of administrators is established, with clusters of protocols. With which two ends can communicate with each other in the same speech.

Answer:- It is preferred to use Web API over WCF, due to the following advantages: 1. Provides much faster and lightweight service 2. Supports multiple data formats 3. Carries full features of HTTP 4. Web API uses SOAP-based protocols, while WCF uses non-SOAP-based services 5. Accessible by a range of clients

Answer:- 1. Set-up the environment: Produce entity, set up conveniences, and split up data 2. Execution: Footstep to apply the framework comprised logging 3. Verification: Check if the authorization works properly 4. Reporting: Report the Progress, malfunction, and bugs found 5. Clean up: Examine the state

Answer:- • Discovery testing • Usability testing • Security testing • Automated testing • Documentation testing

Answer:- 1. Firstly understand the commitment of API. 2. Create an approach list. 3. Apply suitable techniques. 4. Insert parameters according to the requirement. 5. Now test different cases and note the outputs. 6. Match outputs with the expected result.

Answer:- Unit testing is a testing strategy that examines the code before and makes sure if the code is operating correctly without any bugs. In this test cases are formulated for all the functions so we can easily track the fault caused by the change.

Answer:- The common bugs found in API testing are: Unused flags Less reliability Security Problems Performance Issues. Multithreading problems Missing or redo functionality API response time is very high Response Data is not structured rightly The incorrect approach of valid arguments Complexity in connecting and getting a response Collapses to control error conditions appropriately