Drag and Drop Question Match each REST API method to the correct description. Answer:

Question

Exhibit

Answer Area

Explanation

REST API Methods - Drag-and-Drop Explanation

The question maps each HTTP method to its description. Since the descriptions aren't shown, the standard definitions imply this ordering:

Individual Placements

1. POST - Create Sends data to the server to create a new resource. Not idempotent - calling it twice creates two resources. Typically returns 201 Created.

2. PUT - Full Replace Replaces the entire resource at a given URL. Idempotent - sending the same request multiple times has the same effect. Requires sending the complete object, not just changed fields.

3. PATCH - Partial Update Updates only the specified fields of a resource. More efficient than PUT when you only need to change one or two fields. May or may not be idempotent depending on implementation.

4. DELETE - Remove Deletes the specified resource. Idempotent - deleting an already-deleted resource should still return success (or 404).

5. GET - Read Retrieves data without modifying anything. Safe and idempotent. The most common HTTP method.

Common Misconceptions

• PUT vs PATCH: Most common confusion. Remember: PUT = full replacement, PATCH = partial update.
• POST vs PUT: POST creates at a server-chosen URL; PUT creates/replaces at a client-specified URL.
• GET safety: GET must never modify data - it is a "safe" method by HTTP spec.
• Idempotency: POST is the only non-idempotent method here; calling it N times creates N resources.

No community discussion yet for this question.