Batch update patterns in Rest API - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the HTTP method for batch updating resources.

Rest API

fetch('/api/items/batch', { method: '[1]', body: JSON.stringify(data) })

Drag options to blanks, or click blank then click option'

APUT

BGET

CPOST

DDELETE

Attempts:

3 left

💡 Hint

Common Mistakes

Using GET or DELETE methods for updating data.

The PUT method is commonly used for batch updates because it replaces the entire resource or collection.

2fill in blank

medium

Complete the code to set the correct Content-Type header for sending JSON data in a batch update request.

Rest API

fetch('/api/items/batch', { method: 'PUT', headers: { 'Content-Type': '[1]' }, body: JSON.stringify(data) })

Drag options to blanks, or click blank then click option'

Amultipart/form-data

Btext/plain

Capplication/xml

Dapplication/json

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect Content-Type headers like text/plain or application/xml.

The application/json Content-Type header tells the server that the request body contains JSON data.

3fill in blank

hard

Fix the error in the batch update request by choosing the correct URL path segment for batch operations.

Rest API

fetch('/api/items/[1]', { method: 'PUT', body: JSON.stringify(data) })

Drag options to blanks, or click blank then click option'

Abatch

Bmodify

Cchange

Dupdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague or uncommon path segments like 'update' or 'change'.

The path segment batch clearly indicates a batch operation, which is a common REST API pattern.

4fill in blank

hard

Fill both blanks to create a batch update request that sends an array of items and expects a JSON response.

Rest API

fetch('/api/items/batch', { method: '[1]', headers: { 'Content-Type': '[2]' }, body: JSON.stringify(items) })

Drag options to blanks, or click blank then click option'

APUT

Bapplication/json

CPOST

Dtext/html

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST instead of PUT or wrong Content-Type headers.

Use PUT for batch updating and application/json as the Content-Type for JSON data.

5fill in blank

hard

Fill all three blanks to handle a batch update with error checking and JSON response parsing.

Rest API

async function batchUpdate(items) {
  const response = await fetch('/api/items/batch', {
    method: '[1]',
    headers: { 'Content-Type': '[2]' },
    body: JSON.stringify(items)
  });
  if (!response.ok) throw new Error('Batch update failed');
  const result = await response.[3]();
  return result;
}

Drag options to blanks, or click blank then click option'

APUT

Bapplication/json

Cjson

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST instead of PUT, wrong Content-Type, or parsing response as text.

Use PUT for the method, application/json for the Content-Type, and json() to parse the JSON response.

Practice

1. What is the main advantage of using batch update patterns in REST APIs?

easy

A. They only work with GET requests.

B. They allow updating multiple items with a single request, saving time.

C. They require sending separate requests for each item.

D. They increase the number of requests to the server.

Solution

1. Step 1: Understand batch update purpose

   Batch update patterns let you update many items at once instead of one by one.

2. Step 2: Identify the benefit

   This reduces the number of requests and saves time and server resources.

3. Final Answer:

   They allow updating multiple items with a single request, saving time. -> Option B

4. Quick Check:

   Batch update = single request for many items [OK]

Hint: Batch updates reduce requests by combining many updates [OK]

Common Mistakes:

• Thinking batch updates increase requests
• Confusing batch update with single item update
• Assuming batch updates use GET method

2. Which HTTP method is most appropriate for batch updates in REST APIs?

easy

A. GET

B. POST

C. PATCH

D. DELETE

Solution

1. Step 1: Recall HTTP methods for updates

   PATCH is used to partially update resources, suitable for batch updates.

2. Step 2: Eliminate other methods

   GET retrieves data, POST creates new data, DELETE removes data, so they are not best for batch updates.

3. Final Answer:

   PATCH -> Option C

4. Quick Check:

   Batch update uses PATCH method [OK]

Hint: Use PATCH for partial or batch updates [OK]

Common Mistakes:

• Using GET for updates
• Confusing POST with update method
• Using DELETE instead of PATCH

3. Given this JSON payload sent in a PATCH request for batch update:

[{"id":1,"status":"done"},{"id":2,"status":"pending"}]

What does this payload represent?

medium

A. Retrieve items with id 1 and 2.

B. Create two new items with given ids and statuses.

C. Delete items with id 1 and 2.

D. Update status of items with id 1 and 2 to 'done' and 'pending' respectively.

Solution

1. Step 1: Analyze JSON payload

   The payload is an array of objects each with 'id' and 'status' fields, indicating updates.

2. Step 2: Understand PATCH semantics

   PATCH updates existing items partially, so this changes status fields for items with id 1 and 2.

3. Final Answer:

   Update status of items with id 1 and 2 to 'done' and 'pending' respectively. -> Option D

4. Quick Check:

   PATCH with array updates multiple items [OK]

Hint: PATCH with array updates multiple items by id [OK]

Common Mistakes:

• Thinking PATCH creates new items
• Confusing update with delete
• Assuming it retrieves data

4. You send this PATCH request payload to update multiple items:

[{"id":1,"status":"done"}, {"status":"pending"}]

What is the likely problem?

medium

A. Missing 'id' in second object causes update failure or error.

B. The payload is valid and will update all items.

C. Using PATCH instead of POST causes syntax error.

D. The array should be empty for batch updates.

Solution

1. Step 1: Check each object in payload

   The second object lacks 'id', so the server cannot identify which item to update.

2. Step 2: Understand update requirements

   Each update must specify the item to update, usually by 'id'. Missing it causes failure or error.

3. Final Answer:

   Missing 'id' in second object causes update failure or error. -> Option A

4. Quick Check:

   Each update needs an identifier like 'id' [OK]

Hint: Every update object must include an identifier like 'id' [OK]

Common Mistakes:

• Assuming missing 'id' is allowed
• Confusing PATCH with POST errors
• Thinking empty arrays are required

5. You want to batch update user roles but only for users currently active. Which pattern best fits this requirement?

hard

A. Send a PATCH request with an array of user objects filtered to active users only.

B. Send separate PATCH requests for all users regardless of status.

C. Use GET request to update roles for active users.

D. Send a DELETE request with active users to update roles.

Solution

1. Step 1: Identify filtering need

   Only active users should be updated, so filter users before sending batch update.

2. Step 2: Choose correct method and payload

   PATCH with an array of filtered user objects updates roles efficiently in one request.

3. Final Answer:

   Send a PATCH request with an array of user objects filtered to active users only. -> Option A

4. Quick Check:

   Filter then batch update with PATCH [OK]

Hint: Filter data first, then batch update with PATCH [OK]

Common Mistakes:

• Sending updates for all users without filtering
• Using GET or DELETE for updates
• Sending multiple separate requests instead of batch