Which HTTP method is defined for the RAML resource /patients in the example?

Which HTTP method is defined for the RAML resource /patients in the example?

• A. GET
• B. POST
• C. PUT
• D. DELETE

Answer: (A)

This tests how RAML maps HTTP methods to a resource path. In the RAML example, the /patients resource has a get: operation defined, which means the API supports the GET method for that resource. GET is used to retrieve data without changing server state, so the response would provide patient information (a list or a specific item) without creating or modifying anything. The absence of post:, put:, or delete: blocks under this resource means those actions aren’t defined for /patients in the snippet. If the API needed to support creating, updating, or deleting patients, you would see corresponding post:, put:, or delete: blocks under the same path or under a more specific path like /patients/{id}.

This tests how RAML maps HTTP methods to a resource path. In the RAML example, the /patients resource has a get: operation defined, which means the API supports the GET method for that resource. GET is used to retrieve data without changing server state, so the response would provide patient information (a list or a specific item) without creating or modifying anything. The absence of post:, put:, or delete: blocks under this resource means those actions aren’t defined for /patients in the snippet. If the API needed to support creating, updating, or deleting patients, you would see corresponding post:, put:, or delete: blocks under the same path or under a more specific path like /patients/{id}.