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

Question 32 — AB-620 Case Study Set

Paideffort configures Continue on error for the tracking request and stores the outcome in Topic.StatusCode. Which topic design should follow the HTTP node? (Select one answer)

  1. Add a condition that displays tracking data when the status code is 200 and routes other values to a customer-safe fallback message.

  2. Display Topic.ErrorResponse directly whenever the status code isn't 200 so customers can diagnose the carrier response.

  3. Call the carrier a second time for every non-200 response before evaluating whether customer messaging is needed.

  4. Send Topic.TrackingResponse.status immediately and allow the system On Error topic to handle missing values afterward.

Correct answers

  1. Add a condition that displays tracking data when the status code is 200 and routes other values to a customer-safe fallback message.

Explanations

Correct Answer:

Add a condition that displays tracking data when the status code is 200 and routes other values to a customer-safe fallback message.

Explanation:

Paideffort wants the conversation to continue after carrier failures without exposing implementation details. Capturing the HTTP status code allows deterministic branching: successful calls can use the typed response fields, while failed calls can produce a controlled message and next step.

Wrong Answers:

Display Topic.ErrorResponse directly whenever the status code isn't 200 so customers can diagnose the carrier response.

Paideffort prohibits exposing raw API errors and implementation details to customers. The error body can support internal diagnostics but should not be surfaced directly.

Call the carrier a second time for every non-200 response before evaluating whether customer messaging is needed.

A non-200 response can represent a nonexistent tracking number or another deterministic failure. Unconditional retries add load and latency without distinguishing transient failures from valid rejections.

Send Topic.TrackingResponse.status immediately and allow the system On Error topic to handle missing values afterward.

Paideffort configured Continue on error specifically so the current topic can control customer recovery. Accessing response fields before checking the result can lead to missing-data behavior rather than deliberate branching.