Question 38 — AB-620 Case Study Set
Paideffort is evaluating a future address-correction operation.
{
"method": "POST",
"url": "https://api.carrier.example/shipment/address",
"headers": {
"Authorization": "=Environment.CarrierAuthToken"
},
"bodyMode": "JSON Content",
"body": {
"trackingNumber": "=Topic.TrackingNumber",
"postalCode": "=Topic.NewPostalCode"
}
}
The carrier requires JSON and rejects requests whose body format isn't declared. What is missing? (Select one answer)
Add a
Content-Type: application/jsonrequest header.Replace JSON Content with No Content because POST requests shouldn't send structured request bodies.
Move the tracking number from the JSON body into the Authorization header.
Hardcode the carrier bearer token in the header so the API can parse the JSON correctly.
Correct answers
Add a
Content-Type: application/jsonrequest header.
Explanations
Correct Answer:
Add a Content-Type: application/json request header.
Explanation:
Paideffort's prototype sends a JSON body, while the carrier requires the body format to be declared. Adding Content-Type: application/json tells the carrier how to interpret the request payload and addresses the parsing requirement.
Wrong Answers:
Replace JSON Content with No Content because POST requests shouldn't send structured request bodies.
The future carrier operation specifically requires a JSON payload containing the tracking number and postal code. Removing the body would prevent Paideffort from sending those values.
Move the tracking number from the JSON body into the Authorization header.
Authentication metadata and business payload data serve different purposes. The carrier requires the tracking number in the operation's JSON request body.
Hardcode the carrier bearer token in the header so the API can parse the JSON correctly.
Credential storage doesn't determine JSON parsing. Hardcoding the token would also violate Paideffort's credential-management requirement.