A Copilot Studio developer is designing an adaptive card for a leave request form. The form must collect: (1) a start date, (2) an end date, (3) the leave type from a predefined list, and (4) a brief reason in free text. The developer wants to use the most semantically appropriate input elements for each field. Which combination of adaptive card input elements is the best match?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Matching input type to data type is like using the right measuring tool—a date picker for dates, a dropdown for fixed choices, and a text area for free-form answers. Using plain text for everything is like measuring everything with a ruler that only shows whole inches.
Full explanation below image
Full Explanation
Adaptive Cards provide specialized input elements that match the data type being collected. Using the semantically correct element improves user experience, reduces input errors, and ensures data is returned in a consistent, parseable format.
Option A is correct because: Input.Date renders a native date picker appropriate for start/end date collection, ensuring consistent ISO 8601 date format without requiring the user to type dates manually. Input.ChoiceSet with style 'compact' or 'expanded' is ideal for selecting from a predefined list of leave types (Vacation, Sick, Personal, etc.). Input.Text with isMultiline:true provides a resizable text area for the free-text reason field.
Option B is wrong because using Input.Text for all fields forces users to type dates in unpredictable formats, making parsing difficult. A user might type '7/4', 'July 4', or '04-07' for the same date, creating data quality issues downstream. Semantic input types eliminate this ambiguity.
Option C is wrong because Input.Toggle is a binary on/off switch, completely inappropriate for date selection. Input.Number is meant for numeric quantities, not free-text reasons. This combination would produce meaningless data for every field.
Option D is wrong because Input.Time collects a clock time (hours and minutes), not a calendar date. Leave requests require dates, not times of day. Using Input.ChoiceSet with isMultiSelect for a reason field also doesn't make sense—reasons are open-ended, not selected from a list.
Exam tip: Know the adaptive card input element types and their appropriate use cases for the AB-620 exam: Input.Text (free-form), Input.Number (numeric), Input.Date (calendar date), Input.Time (clock time), Input.Toggle (boolean), Input.ChoiceSet (list selection). Match the element type to the data type.