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

Question 27 — AB-620 Case Study Set

Paideffort Global Shipment Tracking Integration
 

Business Requirements

Paideffort operates a customer-service agent in Microsoft Copilot Studio that supports approximately 75,000 customer conversations each month. Customers can already retrieve order information through a Microsoft Dataverse connector and initiate refunds through a reusable agent flow. Paideffort is now adding shipment tracking for a regional carrier whose service exposes a REST endpoint but provides no Power Platform connector, OpenAPI specification, or Model Context Protocol server.

Shipment tracking is required by only one Copilot Studio topic. The integration consists of one API request using the customer-supplied tracking number, followed by a response containing shipment status, estimated delivery date, and last known location. Paideffort wants the smallest maintainable integration that doesn't introduce reusable workflow infrastructure where none is required.

Customer conversations must continue gracefully if the carrier is unavailable, rejects a tracking number, or returns an unexpected response. Raw API errors, credentials, and implementation details must never be shown to customers. Security engineering also requires credentials to be manageable independently in development, test, and production environments.

Technical Architecture

Copilot Studio hosts the customer-facing topics. A Microsoft Foundry project is also used by Paideffort for complex support reasoning. Project-scoped agent operations use the Foundry project endpoint through the Foundry SDK, while direct model operations use an Azure OpenAI endpoint through the OpenAI SDK. A FunctionTool is available for deterministic warranty calculations, an OpenAPI tool exposes a separate returns service, and an Azure Function handles asynchronous refund notifications.

The carrier tracking call doesn't require reasoning, multi-step orchestration, reuse by other topics, an OpenAPI-described REST tool, or an MCP capability. The architecture team therefore places the call directly in the shipment-tracking topic using a Send HTTP Request node.

Tracking Topic Implementation

The customer first provides a tracking number, which is stored in Topic.TrackingNumber. The carrier expects a GET request where the tracking number forms the final path segment. The response body isn't required for the request.

topic: ShipmentTracking
steps:
  - askTrackingNumber:
      output: Topic.TrackingNumber

  - sendHttpRequest:
      method: GET
      url: '"https://api.carrier.example/tracking/" & Topic.TrackingNumber'
      headers:
        X-Carrier-Key: "prod-4f92d1-carrier-key"
      body:
        mode: NoContent
      errorHandling:
        mode: RaiseAnError
      response:
        saveAs: Topic.TrackingResponse

  - sendMessage:
      text: "Your shipment status is available."

Paideffort's carrier documentation provides the following representative response. The operations team wants downstream topic nodes to use only the shipment status, estimated delivery date, and last location.

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

A developer generated a response schema from representative JSON and stored the response in Topic.TrackingResponse. The customer message is being redesigned to display Topic.TrackingResponse.status, Topic.TrackingResponse.estimatedDelivery, and Topic.TrackingResponse.lastLocation.

Carrier Update API Prototype

A separate prototype is being evaluated for a future address-correction operation. The carrier requires a POST request containing JSON and rejects requests whose body format isn't declared.

{
  "method": "POST",
  "url": "https://api.carrier.example/shipment/address",
  "headers": {
    "Authorization": "=Environment.CarrierAuthToken"
  },
  "bodyMode": "JSON Content",
  "body": {
    "trackingNumber": "=Topic.TrackingNumber",
    "postalCode": "=Topic.NewPostalCode"
  }
}

Load and Resilience Observations

During carrier peak periods, successful tracking calls normally complete within 8 to 18 seconds, but occasional valid requests take 35 to 40 seconds. Customer-service leadership prefers a slightly longer wait over prematurely failing requests that the carrier would otherwise complete successfully. Failed calls must remain inside the current conversation and route to a customer-safe recovery message.

One architecture proposal would replace the single HTTP node with an agent flow containing the same one GET request, even though no second topic needs the integration. Another proposal would invoke the Foundry support agent first and ask it to decide whether the carrier call should execute. Platform engineering is evaluating both proposals against latency, maintenance, and operational simplicity.

Future Requirements

Paideffort expects shipment volume to increase during seasonal sales. Governance teams want centralized logs containing HTTP status outcomes without exposing raw carrier responses to customers. Future carriers may publish OpenAPI specifications or reusable APIs that serve multiple topics, which could justify different integration patterns. Security engineering will also tighten credential governance while retaining environment-specific deployment. The current solution should remain simple until those additional reuse or orchestration requirements become concrete.