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

Question 30 — AB-620 Case Study Set

Based on the scenario, which two changes should Paideffort make to the current tracking node to meet its security and customer-experience requirements? (Select two answers)

  1. Move the carrier credential into an environment variable and reference that variable from the request header.

  2. Configure Continue on error and capture the HTTP status code and error response into topic variables.

  3. Keep Raise an error so failed requests always terminate the current tracking topic immediately.

  4. Retain the literal production key because only topic makers can access the authoring canvas.

Correct answers

  1. Move the carrier credential into an environment variable and reference that variable from the request header.

  2. Configure Continue on error and capture the HTTP status code and error response into topic variables.

Explanations

Correct Answer:

Move the carrier credential into an environment variable and reference that variable from the request header.

Configure Continue on error and capture the HTTP status code and error response into topic variables.

Explanation:

Paideffort requires credentials to be independently manageable across environments and hidden from the topic canvas, making an environment variable appropriate. The customer-facing conversation must also remain active when carrier calls fail. Continue on error allows Paideffort to capture the failure state and route the customer to a controlled recovery branch.

Wrong Answers:

Keep Raise an error so failed requests always terminate the current tracking topic immediately.

Paideffort specifically requires tracking failures to remain within the customer conversation and produce a useful recovery path. Raising an error routes execution away from that controlled topic behavior.

Retain the literal production key because only topic makers can access the authoring canvas.

The requirement is to keep credentials out of the canvas and manage them independently across deployment environments. A literal key remains visible to authorized makers and creates credential-management problems.