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

Question 51 — AB-620 Case Study Set

Review the HTTP configuration used by Paideffort before the regulatory response is transformed.

- captureQuestion:
    output: Topic.ComplianceQuestion

- sendHttpRequest:
    method: GET
    url: "https://regulatory.paideffort.internal/regulations?limit=8"
    response:
      saveAs: Topic.RegResponse

The API supports relevance ranking when the user's question is supplied in a query parameter. What should be improved? (Select one answer)

  1. Add the encoded value of Topic.ComplianceQuestion to the API query so the returned records are ranked for the current compliance question.

  2. Increase limit substantially so the generative answers node can determine relevance across the entire regulatory catalog.

  3. Remove Topic.ComplianceQuestion from the topic because the API response can be ranked using only record update timestamps.

  4. Replace the GET request with a Foundry agent invocation so the model can decide which API records should have been returned.

Correct answers

  1. Add the encoded value of Topic.ComplianceQuestion to the API query so the returned records are ranked for the current compliance question.

Explanations

Correct Answer:

Add the encoded value of Topic.ComplianceQuestion to the API query so the returned records are ranked for the current compliance question.

Explanation:

Paideffort's pilot shows that update order can place the strongest regulation outside the records consumed by Custom data. Supplying the officer's question to the API enables relevance ranking before the results reach Copilot Studio, increasing the likelihood that the first three records contain the strongest grounding evidence.

Wrong Answers:

Increase limit substantially so the generative answers node can determine relevance across the entire regulatory catalog.

Returning more records doesn't solve Paideffort's positional limit. Records beyond the first three won't contribute merely because the API returns a larger collection.

Remove Topic.ComplianceQuestion from the topic because the API response can be ranked using only record update timestamps.

The question provides the context necessary for relevance ranking. Recency alone already produced weaker ordering during Paideffort's pilot.

Replace the GET request with a Foundry agent invocation so the model can decide which API records should have been returned.

The regulatory API already supports query-based ranking. Using deterministic retrieval is simpler and avoids unnecessary model processing.