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

Question 11 — AB-620 Case Study Set

Paideffort's topic currently continues directly from the Adaptive Card to the leave-creation tool.

trigger: LeaveRequest
steps:
  - getRegionalLeaveTypes:
      output: Topic.AvailableLeaveTypes
  - askWithAdaptiveCard:
      card: leaveRequestCard
  - callTool:
      name: CreateLeaveRequest
      inputs:
        leaveType: Topic.input1
        startDate: Topic.input2
        endDate: Topic.input3
        reason: Topic.input4

What should be improved before CreateLeaveRequest is called? (Select one answer)

  1. Insert a Condition step that verifies the required card outputs contain values and routes incomplete or dismissed submissions away from the tool call.

  2. Insert another Ask with Adaptive Card step containing the same fields so the topic always receives two copies of the leave request.

  3. Insert a Foundry agent invocation that infers values for any missing card fields before the leave-creation tool receives the request.

  4. Insert a Send a message step that prints the variables while allowing the tool call to continue regardless of whether they contain values.

Correct answers

  1. Insert a Condition step that verifies the required card outputs contain values and routes incomplete or dismissed submissions away from the tool call.

Explanations

Correct Answer:

Insert a Condition step that verifies the required card outputs contain values and routes incomplete or dismissed submissions away from the tool call.

Explanation:

Paideffort requires dismissed forms to be handled without invoking the Azure Function with incomplete data. The current YAML moves directly from the Adaptive Card to CreateLeaveRequest. A Condition between those operations can inspect required outputs and route empty submissions to a recovery branch.

Wrong Answers:

Insert another Ask with Adaptive Card step containing the same fields so the topic always receives two copies of the leave request.

Repeating the same form doesn't deterministically establish whether a valid submission occurred and would create unnecessary interaction. Paideffort needs validation and branching, not duplicate collection.

Insert a Foundry agent invocation that infers values for any missing card fields before the leave-creation tool receives the request.

The missing values represent employee-supplied business data. Paideffort shouldn't fabricate leave dates or categories through model inference when the form has been dismissed or left incomplete.

Insert a Send a message step that prints the variables while allowing the tool call to continue regardless of whether they contain values.

Displaying the variables doesn't stop an invalid downstream invocation. Paideffort requires the workflow to prevent incomplete submissions from reaching the leave-creation service.