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

Question 17 — AB-620 Case Study Set

Based on the scenario, Paideffort is considering three channel-specific card definitions even though their business content is identical and the newer web layout provides no measurable benefit. Which architecture decision best satisfies the current requirements? (Select one answer)

  1. Adopt one version 1.5 card for all three channels and introduce channel-specific variants only if a future requirement provides sufficient benefit.

  2. Keep all three channel-specific cards because every production channel should always have a dedicated Adaptive Card definition.

  3. Adopt the version 1.6 web card for all channels and use the Foundry agent to generate fallback content when rendering fails.

  4. Remove Adaptive Cards from Teams and Live Chat and provide the structured leave experience only through the internal web portal.

Correct answers

  1. Adopt one version 1.5 card for all three channels and introduce channel-specific variants only if a future requirement provides sufficient benefit.

Explanations

Correct Answer:

Adopt one version 1.5 card for all three channels and introduce channel-specific variants only if a future requirement provides sufficient benefit.

Explanation:

Paideffort prioritizes predictable rendering and low maintenance, and product management has found no meaningful outcome that depends on version 1.6 styling. One version 1.5 design satisfies the compatibility requirements for Teams and Live Chat while also remaining usable on the web channel. Channel-specific variants should be reserved for cases where the additional web capability justifies the operational overhead.

Wrong Answers:

Keep all three channel-specific cards because every production channel should always have a dedicated Adaptive Card definition.

Paideffort's card content is currently equivalent across channels. Maintaining three definitions creates unnecessary synchronization and governance overhead without providing a business benefit.

Adopt the version 1.6 web card for all channels and use the Foundry agent to generate fallback content when rendering fails.

Model reasoning doesn't correct renderer incompatibility. Paideffort would still deploy a schema version unsupported by Teams and Live Chat.

Remove Adaptive Cards from Teams and Live Chat and provide the structured leave experience only through the internal web portal.

Paideffort requires the essential employee interaction to remain available through its supported production channels, including Teams and the upcoming Live Chat deployment.