Question 7 — AB-620 Case Study Set
Paideffort's governance team wants topic expressions, tool mappings, and audit records to be understandable without translating generic identifiers such as input1 and input3. Which change best addresses this requirement? (Select one answer)
Rename the card input IDs to leaveType, startDate, endDate, and leaveReason and use the corresponding Topic variables downstream.
Keep input1 through input4 but rename only the visible labels because labels determine the resulting topic variable names.
Keep input1 through input4 and create four Foundry agent instructions that describe the business meaning of each identifier.
Rename the Submit button to include all four field names because the Submit title determines the topic variables created from the card.
Correct answers
Rename the card input IDs to leaveType, startDate, endDate, and leaveReason and use the corresponding Topic variables downstream.
Explanations
Correct Answer:
Rename the card input IDs to leaveType, startDate, endDate, and leaveReason and use the corresponding Topic variables downstream.
Explanation:
Paideffort's downstream tool mapping and future governance dashboard benefit from descriptive identifiers. Adaptive Card input IDs determine the associated topic outputs, so names such as leaveType, startDate, endDate, and leaveReason make subsequent expressions and operational tracing substantially clearer.
Wrong Answers:
Keep input1 through input4 but rename only the visible labels because labels determine the resulting topic variable names.
Labels improve what employees see, but Paideffort's downstream variables originate from the input IDs. Changing labels alone doesn't solve the ambiguous identifier problem in expressions and audit records.
Keep input1 through input4 and create four Foundry agent instructions that describe the business meaning of each identifier.
The ambiguity exists in deterministic topic variables and tool mappings. Adding agent instructions introduces complexity without correcting the identifiers that governance teams must trace.
Rename the Submit button to include all four field names because the Submit title determines the topic variables created from the card.
The Submit title controls the user-facing button label. It doesn't replace the input IDs that identify the submitted values.