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

Question 3 — AB-620 Case Study Set

Given that the system uses an original request card, a retry card, and a later confirmation card, which two changes should Paideffort implement to reliably associate a submitted action with the card that generated it? (Select two answers)

  1. Add a unique action identifier to the data payload of each relevant Action.Submit element.

  2. Validate the returned action identifier before processing the submitted response.

  3. Assign identical Submit button titles to all cards so that users experience consistent labeling.

  4. Use the same Adaptive Card input IDs across all cards so that submitted actions resolve to one variable set.

Correct answers

  1. Add a unique action identifier to the data payload of each relevant Action.Submit element.

  2. Validate the returned action identifier before processing the submitted response.

Explanations

Correct Answer:

Add a unique action identifier to the data payload of each relevant Action.Submit element.

Validate the returned action identifier before processing the submitted response.

Explanation:

Paideffort can have several submitted cards present in the same conversation, and employees might interact with an older card. A unique identifier such as actionSubmitId in each submit action's data provides the response with card/action identity. Processing logic must then validate that identifier so the response is routed to the intended workflow.

Wrong Answers:

Assign identical Submit button titles to all cards so that users experience consistent labeling.

The button title is primarily presentation text. Identical labels don't provide Paideffort with a reliable machine-readable way to distinguish the original form, retry form, and confirmation response.

Use the same Adaptive Card input IDs across all cards so that submitted actions resolve to one variable set.

Reusing IDs can make responses more ambiguous rather than identifying which card produced them. Paideffort requires correlation to a specific card and action, which calls for distinct submit metadata and validation.