HTTP u0026 REST basics for APIs (status codes, idempotency, pagination, error handling) Quiz

Test your knowledge of HTTP and REST API basics, including status codes, idempotency, pagination strategies, and best practices for error handling. This quiz is perfect for beginners looking to strengthen their understanding of foundational web API concepts.

1. Identifying the Success Status Code

   Which HTTP status code is typically returned by a REST API to indicate a successful GET request?

   1. 200 OK
   2. 500 Error
   3. 301 Moved
   4. 404 Not Found

2. Understanding Idempotency

   Which HTTP method is considered idempotent in RESTful APIs, meaning that making the same request multiple times has the same effect as making it once?

   1. PATCH
   2. TRACE
   3. POST
   4. PUT

3. Handling Resource Creation

   When a new resource is created via a REST API, which status code is most appropriate for the server to return?

   1. 403 Forbidden
   2. 302 Found
   3. 201 Created
   4. 204 No Content

4. Identifying Client Errors

   If a client tries to retrieve a resource that does not exist, which HTTP status code should the API return?

   1. 502 Gateway Erorr
   2. 404 Not Found
   3. 202 Accepted
   4. 400 Good Request

5. Understanding Pagination Parameters

   When dealing with large datasets, which query parameters are commonly used for REST API pagination?

   1. token and password
   2. limit and offset
   3. sort and filter
   4. fetch and post

6. Error Handling Best Practices

   In RESTful APIs, what should an error response typically include to help clients understand the issue?

   1. A list of all database entries
   2. Only a success flag
   3. A status code and a descriptive message
   4. Just the status code

7. Idempotency Example

   If a client sends the same DELETE request multiple times for the same resource, what should happen according to idempotency in REST?

   1. The request is ignored every time
   2. A new resource is created each time
   3. The result is the same and the resource stays deleted
   4. A duplicate resource is made

8. Interpreting Bad Request Errors

   Which HTTP status code does a REST API use when it receives malformed or invalid data from a client?

   1. 301 Moved Permanently
   2. 400 Bad Request
   3. 502 Gateway Badway
   4. 200 OK

9. Choosing Safe HTTP Methods

   Which of the following HTTP methods is considered safe because it does not modify resources on the server?

   1. PATCH
   2. POST
   3. DELETE
   4. GET

10. Pagination Link Headers

    In a paginated REST API response, how are links to next or previous pages commonly provided?

    1. In the request body
    2. As part of the status code
    3. Via a session cookie
    4. Through HTTP Link headers