Question 24 — AB-620 Case Study Set
Review the Adaptive Card definition currently deployed by Paideffort.
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.6",
"body": [
{
"type": "Container",
"layouts": [
{
"type": "Layout.Flow"
}
],
"items": [
{
"type": "TextBlock",
"text": "Annual leave: 14 days"
}
]
}
],
"actions": [
{
"type": "Action.Execute",
"title": "View details",
"verb": "viewLeaveDetails"
}
]
}
Which two aspects should Paideffort change to meet the current cross-channel production requirement? (Select two answers)
Reduce the declared schema to version 1.5 and remove or redesign features that depend on version 1.6.
Replace Action.Execute with Action.Submit for the cross-channel action.
Increase the schema to version 2.0 so older channels automatically negotiate a compatible representation.
Retain version 1.6 and remove the
$schemaproperty because the version check is caused by the schema URL.
Correct answers
Reduce the declared schema to version 1.5 and remove or redesign features that depend on version 1.6.
Replace Action.Execute with Action.Submit for the cross-channel action.
Explanations
Correct Answer:
Reduce the declared schema to version 1.5 and remove or redesign features that depend on version 1.6.
Replace Action.Execute with Action.Submit for the cross-channel action.
Explanation:
Paideffort's common production targets include Teams and Live Chat, which require the card to remain within version 1.5 capabilities. The existing card also uses Action.Execute, which doesn't meet Paideffort's web-channel compatibility requirement. Both changes are therefore necessary for the shared card strategy.
Wrong Answers:
Increase the schema to version 2.0 so older channels automatically negotiate a compatible representation.
Increasing the declared schema would move Paideffort further beyond the capabilities of the target renderers. It doesn't cause Teams or Live Chat to automatically support newer elements.
Retain version 1.6 and remove the $schema property because the version check is caused by the schema URL.
The compatibility problem is driven by the declared card version and the features used, not by whether the schema reference URL appears in the JSON.