Question 37 — AB-620 Case Study Set
Review Paideffort's current tracking-node configuration.
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
Which two changes are required to align this implementation with Paideffort's stated production requirements? (Select two answers)
Replace the literal carrier key with a reference to an environment variable.
Change error handling to Continue on error and capture failure information for downstream branching.
Change the GET request body from No Content to JSON Content containing the tracking number.
Replace the dynamic URL with a static URL because topic variables shouldn't be used in HTTP addresses.
Correct answers
Replace the literal carrier key with a reference to an environment variable.
Change error handling to Continue on error and capture failure information for downstream branching.
Explanations
Correct Answer:
Replace the literal carrier key with a reference to an environment variable.
Change error handling to Continue on error and capture failure information for downstream branching.
Explanation:
Paideffort requires credentials to remain outside the authoring canvas and to be manageable across environments, so the literal key should be moved into an environment variable. The customer conversation must also survive HTTP failures, requiring Continue on error plus captured status and error variables.
Wrong Answers:
Change the GET request body from No Content to JSON Content containing the tracking number.
The carrier expects the tracking number as the final URL path segment. The current GET request correctly uses no request body.
Replace the dynamic URL with a static URL because topic variables shouldn't be used in HTTP addresses.
The carrier endpoint explicitly requires the customer-specific tracking number in the URL. A Power Fx expression using Topic.TrackingNumber is appropriate for this requirement.