Partial success handling in Rest API - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to return a 207 status code for partial success.

Rest API

response.status_code = [1]

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

A500

B207

C404

D200

Attempts:

3 left

💡 Hint

Common Mistakes

Using 200 which means full success

Using 404 which means not found

Using 500 which means server error

The HTTP status code 207 indicates a multi-status response, often used for partial success.

2fill in blank

medium

Complete the code to include a list of failed items in the JSON response.

Rest API

response.json = {"failed_items": [1]

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

A["item1", "item2"]

B{}

C[]

DNone

Attempts:

3 left

💡 Hint

Common Mistakes

Using None which is not JSON serializable

Using empty list which means no failures

Using empty dict which is wrong type

The failed items should be a list of strings representing which items failed.

3fill in blank

hard

Fix the error in the code to properly handle partial success response.

Rest API

if failed_items:
    return [1](json={"failed": failed_items}, status=207)
else:
    return success_response()

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

Arender_template

Bjsonify

Cmake_response

Dredirect

Attempts:

3 left

💡 Hint

Common Mistakes

Using jsonify which cannot set status code directly

Using render_template which is for HTML

Using redirect which is for URL redirection

make_response allows setting both JSON content and status code together.

4fill in blank

hard

Fill both blanks to create a partial success response with a message and failed items list.

Rest API

response = [1]({"message": "Partial success", "failed": [2], status=207)

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

Amake_response

Bjsonify

C[]

D["file1", "file2"]

Attempts:

3 left

💡 Hint

Common Mistakes

Using jsonify which cannot set status code directly

Using empty list for failed items

make_response creates the response with status code; the failed list shows which files failed.

5fill in blank

hard

Fill all three blanks to build a detailed partial success response with status, message, and failed items count.

Rest API

response = [1]({"status": [2], "message": "Partial success", "failed_count": [3], status=207)

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

Amake_response

B207

Clen(failed_items)

Djsonify

Attempts:

3 left

💡 Hint

Common Mistakes

Using jsonify instead of make_response

Using string '207' instead of number 207

Using a wrong count value

make_response creates the response; status is 207; failed_count is the length of failed items list.

Practice

1. What does HTTP 207 Multi-Status indicate in REST API partial success handling?

easy

A. Some parts of the request succeeded while others failed

B. The entire request failed due to server error

C. The request was redirected to another URL

D. The request was successful with no errors

Solution

1. Step 1: Understand HTTP 207 Multi-Status meaning

   HTTP 207 is used to report multiple status codes for different parts of a single request.

2. Step 2: Relate to partial success handling

   This status code indicates that some parts succeeded and others failed, providing detailed results.

3. Final Answer:

   Some parts of the request succeeded while others failed -> Option A

4. Quick Check:

   HTTP 207 = Partial success [OK]

Hint: 207 means mixed results, not full success or failure [OK]

Common Mistakes:

• Confusing 207 with 200 OK
• Thinking 207 means full failure
• Assuming 207 is a redirect status

2. Which of the following is the correct way to represent partial success in a REST API response?

easy

A. HTTP 404 with error message

B. HTTP 200 with empty body

C. HTTP 207 with JSON detailing success and failure

D. HTTP 500 with stack trace

Solution

1. Step 1: Identify correct HTTP status for partial success

   HTTP 207 Multi-Status is designed to show multiple results in one response.

2. Step 2: Confirm response format

   Using JSON to detail which parts succeeded or failed is the standard approach.

3. Final Answer:

   HTTP 207 with JSON detailing success and failure -> Option C

4. Quick Check:

   207 + JSON = Partial success response [OK]

Hint: Use 207 with JSON for partial success, not 200 or errors [OK]

Common Mistakes:

• Using 200 OK without details
• Returning 404 for partial success
• Sending server error 500 instead of partial status

3. Given this partial success JSON response, what is the status of item with ID 3?

{
  "responses": [
    {"id": 1, "status": "success"},
    {"id": 2, "status": "failure", "error": "Invalid data"},
    {"id": 3, "status": "success"}
  ]
}

medium

A. Failure due to invalid data

B. Success

C. Unknown status

D. Pending

Solution

1. Step 1: Locate item with ID 3 in JSON

   Item with ID 3 has "status": "success" in the responses array.

2. Step 2: Interpret the status value

   The status "success" means the operation for item 3 succeeded.

3. Final Answer:

   Success -> Option B

4. Quick Check:

   ID 3 status = success [OK]

Hint: Check the status field for the item ID in JSON [OK]

Common Mistakes:

• Confusing failure of other items with this one
• Assuming missing error means failure
• Ignoring the status field

4. You receive this HTTP response code and body from a batch update API:

HTTP/1.1 207 Multi-Status
{
  "results": [
    {"item": "A", "status": "success"},
    {"item": "B", "status": "fail", "error": "Timeout"}
  ]
}

What is the main issue in this response?

medium

A. Incorrect HTTP status code for partial success

B. JSON format is invalid

C. Missing Content-Type header

D. The status value "fail" should be "failure" or "error"

Solution

1. Step 1: Check HTTP status code usage

   HTTP 207 Multi-Status is correct for partial success.

2. Step 2: Verify status field values

   Common practice uses "success" and "failure" or "error"; "fail" is inconsistent and may cause confusion.

3. Final Answer:

   The status value "fail" should be "failure" or "error" -> Option D

4. Quick Check:

   Status values must be consistent and clear [OK]

Hint: Use standard status words like 'success' and 'failure' [OK]

Common Mistakes:

• Thinking 207 is wrong here
• Ignoring inconsistent status wording
• Assuming JSON is invalid without checking

5. You design a REST API endpoint that processes a list of user updates. Some updates succeed, others fail due to validation errors. How should you structure the response to clearly communicate partial success?

hard

A. Return HTTP 207 with a JSON array showing each user's update status and error if any

B. Return HTTP 400 with a generic error message for all failures

C. Return HTTP 200 with a simple success message ignoring failures

D. Return HTTP 500 with server error details

Solution

1. Step 1: Identify the need for partial success reporting

   Since some updates succeed and others fail, the response must show both results clearly.

2. Step 2: Choose appropriate HTTP status and response format

   HTTP 207 Multi-Status with detailed JSON per user update is the best practice to communicate partial success.

3. Final Answer:

   Return HTTP 207 with a JSON array showing each user's update status and error if any -> Option A

4. Quick Check:

   207 + detailed JSON = clear partial success [OK]

Hint: Use 207 and detailed JSON for mixed success/failure results [OK]

Common Mistakes:

• Ignoring failed updates in response
• Using 200 OK without details
• Returning generic errors instead of per-item status