Which HTTP method should be used when updating a full resource profile rather than just a single field?

Which HTTP method should be used when updating a full resource profile rather than just a single field?

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

Answer: (C)

When you need to replace the entire resource with a new representation, use the method designed for a full replacement. That method sends the complete updated profile in the request body and replaces the existing resource at the target URL. It’s idempotent, meaning repeating the same request yields the same end state, which is exactly what you want for a full update. If you only want to change a single field, a partial update is more appropriate. The partial-update method applies just the changes you provide, leaving the rest of the resource intact. The other methods don’t fit this scenario: retrieval methods don’t modify data, and a non-idempotent create/update approach isn’t aligned with replacing the full resource.

When you need to replace the entire resource with a new representation, use the method designed for a full replacement. That method sends the complete updated profile in the request body and replaces the existing resource at the target URL. It’s idempotent, meaning repeating the same request yields the same end state, which is exactly what you want for a full update.

If you only want to change a single field, a partial update is more appropriate. The partial-update method applies just the changes you provide, leaving the rest of the resource intact.

The other methods don’t fit this scenario: retrieval methods don’t modify data, and a non-idempotent create/update approach isn’t aligned with replacing the full resource.