Which statement about the REST request body is true?

Which statement about the REST request body is true?

• A. The request body is used to identify the resource by ID in every case.
• B. The request body should always be placed in the URL.
• C. The request body is optional for POST requests that create resources.
• D. The request body is the primary place for sending complex data for create or update operations.

Answer: (D)

In REST, the request body carries the resource representation you want to create or update. For a create operation, you typically POST to a collection endpoint and include the new object’s fields (as JSON, XML, etc.) in the body. For an update, you send the updated representation in the body to the specific resource URL, using PUT or PATCH. The URL identifies which resource to operate on, while the body provides the actual data that defines or changes that resource. This makes the body the primary place for sending complex data used in create or update operations. The other statements don’t fit typical REST practices: identifying a resource by its ID is usually done in the URL rather than the body; placing the body in the URL would not be practical for large or complex data; and while some APIs might allow creating with an empty body, the common, correct approach is to supply the resource representation in the body.

In REST, the request body carries the resource representation you want to create or update. For a create operation, you typically POST to a collection endpoint and include the new object’s fields (as JSON, XML, etc.) in the body. For an update, you send the updated representation in the body to the specific resource URL, using PUT or PATCH. The URL identifies which resource to operate on, while the body provides the actual data that defines or changes that resource. This makes the body the primary place for sending complex data used in create or update operations. The other statements don’t fit typical REST practices: identifying a resource by its ID is usually done in the URL rather than the body; placing the body in the URL would not be practical for large or complex data; and while some APIs might allow creating with an empty body, the common, correct approach is to supply the resource representation in the body.