Operations wants one canvas that shows DNA Center wireless health and posts a Webex ChatOps alert when the wireless score drops. Which design stays inside the official 3.x construction?
Select an answer to reveal the explanation.
Short Explanation
One board can marry two official families—DNA health on the wall, Webex nudge when the score dips—like a scoreboard plus a pager. ACI, ISE, or SD-WAN tiles invent products this task does not number.
Full Explanation
Official 3.x construction allows one canvas to join DNA Center wireless health retrieve with a Webex ChatOps notify when the wireless score drops. Both are numbered Cisco platform API families on the same board: health is collected and presented; ChatOps is the notify path when the score crosses a threshold. That pairing stays inside the construction objective without dragging in unrelated fabrics.
Adding ACI fabric health, ISE posture, and SD-WAN path tiles as required third-party hops invents mandatory platforms the wireless-plus-ChatOps scenario does not require and blurs the tested join. Replacing DNA and Webex with only AppDynamics browser RUM omits Cisco platform APIs entirely, so the canvas no longer demonstrates the construction skill. Requiring UCS Manager XML for every wireless score tile before ChatOps may fire couples wireless health to a compute-manager API that is not part of this DNA–Webex design.
Exam caveat: joining two official families on one board is allowed; stuffing every Cisco product onto the same canvas is not what the objective asks. Operational check: confirm the board retrieves DNA wireless health, evaluates the score, and posts a Webex ChatOps alert on drop—using those APIs—without depending on ACI, ISE, SD-WAN, or UCS Manager for the wireless path.