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

Question 29 — AB-620 Case Study Set

Given that the system must construct the carrier endpoint from the tracking number collected earlier in the topic, which URL configuration satisfies Paideffort's requirement? (Select one answer)

  1. "https://api.carrier.example/tracking/" & Topic.TrackingNumber

  2. "https://api.carrier.example/tracking/Topic.TrackingNumber"

  3. "https://api.carrier.example/tracking/" + "TrackingNumber"

  4. Topic.TrackingNumber & "https://api.carrier.example/tracking/"

Correct answers

  1. "https://api.carrier.example/tracking/" & Topic.TrackingNumber

Explanations

Correct Answer:

"https://api.carrier.example/tracking/" & Topic.TrackingNumber

Explanation:

Paideffort stores the customer-supplied identifier in Topic.TrackingNumber, and the carrier expects that value as the final URL path segment. The Power Fx concatenation combines the fixed endpoint with the runtime topic variable.

Wrong Answers:

"https://api.carrier.example/tracking/Topic.TrackingNumber"

This places the variable name inside a literal string, so the carrier would receive Topic.TrackingNumber as text rather than the customer's actual tracking value.

"https://api.carrier.example/tracking/" + "TrackingNumber"

This combines literal strings rather than using Paideffort's topic variable and also doesn't use the intended Power Fx concatenation expression.

Topic.TrackingNumber & "https://api.carrier.example/tracking/"

The operands are reversed, producing a URL with the tracking number before the carrier endpoint rather than as its final path segment.