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

Question 5 — AB-620 Case Study Set

Based on the scenario, Paideffort expects leave categories to vary by employee region and already retrieves them before displaying the form. Which implementation best meets the runtime behavior and optimization requirements? (Select one answer)

  1. Bind the Input.ChoiceSet choices property to Topic.AvailableLeaveTypes after ensuring the table contains title and value columns.

  2. Create a separate Question node for every leave category and branch according to which regional option the employee confirms.

  3. Hardcode every regional leave category into one Adaptive Card and hide unavailable options by changing the card's explanatory text.

  4. Ask the Foundry policy agent to regenerate the entire leave form as natural-language output whenever the employee opens the topic.

Correct answers

  1. Bind the Input.ChoiceSet choices property to Topic.AvailableLeaveTypes after ensuring the table contains title and value columns.

Explanations

Correct Answer:

Bind the Input.ChoiceSet choices property to Topic.AvailableLeaveTypes after ensuring the table contains title and value columns.

Explanation:

Paideffort already retrieves the employee's regional categories into Topic.AvailableLeaveTypes, and the option list genuinely varies by region. Binding that table directly to the ChoiceSet provides the current options without creating extra user turns or requiring unnecessary generative processing.

Wrong Answers:

Create a separate Question node for every leave category and branch according to which regional option the employee confirms.

This would increase topic complexity and conversation turns while duplicating data that Paideffort already retrieves dynamically from its HR service.

Hardcode every regional leave category into one Adaptive Card and hide unavailable options by changing the card's explanatory text.

Paideffort's valid options vary at runtime. A static list risks presenting categories that don't apply to the current employee and duplicates policy data inside the topic.

Ask the Foundry policy agent to regenerate the entire leave form as natural-language output whenever the employee opens the topic.

The required values are structured form inputs, and the valid categories already exist as topic data. Generating the form through an agent adds avoidable model work and doesn't provide the direct structured binding Paideffort needs.