Skip to main content
  1. Public practice questions
  2. AB-620 Practice Exams | AI Agent Builder Associate
  3. AB-620 Case Study Set

Question 39 — AB-620 Case Study Set

Paideffort's carrier documentation provides this representative response:

{
  "trackingNumber": "PAI-83492105",
  "status": "In transit",
  "estimatedDelivery": "2026-09-08",
  "lastLocation": "Accra Distribution Hub",
  "internalRouteCode": "GH-AC-17",
  "carrierDiagnostic": "SORT_COMPLETE"
}

What should Paideffort do so the topic can reliably reference status, estimatedDelivery, and lastLocation after the HTTP request? (Select one answer)

  1. Generate the response data type from representative JSON and save the response to a topic variable.

  2. Store the complete response as raw display text and ask the Foundry agent to extract the three fields after every request.

  3. Create three additional HTTP requests so each required property is retrieved independently from the carrier.

  4. Remove all fields except the three customer-facing values from the carrier's API before Copilot Studio receives the response.

Correct answers

  1. Generate the response data type from representative JSON and save the response to a topic variable.

Explanations

Correct Answer:

Generate the response data type from representative JSON and save the response to a topic variable.

Explanation:

Paideffort needs structured downstream access to the carrier response. Generating the response schema from representative JSON allows Copilot Studio to expose typed fields with Power Fx and IntelliSense, after which the response can be stored in Topic.TrackingResponse.

Wrong Answers:

Store the complete response as raw display text and ask the Foundry agent to extract the three fields after every request.

This would add unnecessary model latency and nondeterministic parsing to a response whose JSON structure is already known.

Create three additional HTTP requests so each required property is retrieved independently from the carrier.

The carrier already returns all required values in one response. Additional calls would increase latency and external API load without improving the integration.

Remove all fields except the three customer-facing values from the carrier's API before Copilot Studio receives the response.

Paideffort doesn't control the carrier's response contract. It can instead define and use the fields needed by its topic while ignoring unnecessary response values.