During a helpdesk escalation, a housing authority needs one laptop’s fabric path and authentication trail quickly. Which Assurance capability best matches that request?
Select an answer to reveal the explanation.
Short Explanation
Helpdesk does not need the whole city’s map—they need that one laptop’s story. Client 360-style Assurance pulls path, health, and auth context for a single endpoint. That beats exporting the LSDB or rebooting control planes to feel productive.
Full Explanation
During a housing-authority helpdesk escalation that needs one laptop’s fabric path and authentication trail quickly, Client 360-style Assurance views best match the request. They pull a single endpoint’s path, health, and auth-related context so agents and network ops share one correlated story instead of hunting across devices blindly.
Exporting the full underlay LSDB to CSV for the helpdesk to diff by hand is slow, error-prone, and usually irrelevant to a single client auth/path issue.
Rebooting all control-plane nodes to refresh every map-cache campus-wide is destructive and disproportionate.
Disabling CDP on the user’s access port to force a clean restart does not provide the authentication/path trail and may hinder topology visibility.
Exam caveat: Assurance depends on telemetry health—if sensors are red, fix telemetry before trusting empty client views.
Operational check: open Client 360 for the laptop, note onboarding stage and path, and cross-check AAA/edge only as needed. Attach the Client 360 summary to the helpdesk ticket for civic auditability. In municipal operations, record the rationale in the change ticket so future on-call staff know which control was chosen and which failure modes the rejected options would create for city services. Re-validate after the next maintenance window that the same control still holds under the platform code and policy revisions used by the civic network team.