RESTful API Design Quiz Quiz

1. HTTP Method for Updates

   Which HTTP method is typically used to update an existing resource in a RESTful API?

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

2. Resource Identification

   What is the common way to uniquely identify a resource in a RESTful API?

   1. Through request headers
   2. By its metadata
   3. Using a URL
   4. Via cookies
   5. With JavaScript

3. Idempotency of GET

   Which of the following HTTP methods is considered idempotent?

   1. POST
   2. PATCH
   3. GET
   4. ALL
   5. HEAD

4. Statelessness in REST

   What does 'statelessness' mean in the context of RESTful APIs?

   1. The server does not hold any state about the client session on the server.
   2. The server always returns a state code.
   3. The client must send all necessary information in each request.
   4. Both the first and third option
   5. The API server is unable to track the clients actions

5. HATEOAS Explained

   What does HATEOAS stand for in RESTful API design?

   1. Hypertext As The Engine Of Application State
   2. Hypertext As The Engine Of All Services
   3. Hypermedia As The Engine Of Application State
   4. Hypermedia As The Engine Of All Services
   5. Hypertext Application Transfer Engine Of Application State

6. HTTP Status Code for Success

   Which HTTP status code generally indicates a successful creation of a resource?

   1. 200 OK
   2. 201 Created
   3. 204 No Content
   4. 400 Bad Request
   5. 500 Internal Server Error

7. Using Flask for API

   Which Flask library is commonly used for defining request data structures and validating API requests?

   1. Flask-RESTful
   2. Marshmallow
   3. Flask-SQLAlchemy
   4. Flask-Login
   5. Request Library

8. Error Handling in REST

   What is the best approach for handling API errors in a RESTful API, ensuring the client receives helpful information?

   1. Return a generic 500 error
   2. Return a custom error code with a detailed message in the response body
   3. Raise an exception and let the server handle it
   4. Log the error and continue processing
   5. Ignore the error as it is not the clients issue

9. API Versioning

   What is a common practice for versioning a RESTful API?

   1. Using query parameters
   2. Using a custom header
   3. Using a date-based versioning scheme
   4. Including the version number in the URL
   5. No need for versioning

10. HTTP DELETE with Payload

    Is it acceptable to send a payload with an HTTP DELETE request?

    1. Yes, always
    2. No, never
    3. Only for logging purposes
    4. It depends on the API design and server implementation
    5. Only if its encrypted