Two civic tickets land at once: how Horizon entitlements work, and error 12345 after a 2103 upgrade. How should the associate match resource type?
Select an answer to reveal the explanation.
Short Explanation
Owner's manual versus recall notice: Docs explain how entitlements are supposed to work, and KB tracks a numbered post-upgrade fault. Swapping those classes, or grabbing Boxer or NSX logs, misses the match. Pair the how-it-works ticket with documentation and the error ticket with Knowledge Base.
Full Explanation
Resource matching for two simultaneous civic tickets requires product documentation when the ask is how Horizon entitlements work, and Knowledge Base when the ask is a known error such as code 12345 after a 2103 upgrade. Documentation explains intended configuration and behavior; Knowledge Base catalogs known issues and resolutions. Split-brain ticket handling in city service desks improves when analysts label each request with the matching official resource type before gathering logs. Reversing that pairing—using Knowledge Base for architecture theory and Tech Zone only for a single error code—misassigns resource classes. Workspace ONE Boxer logs address mail-client symptoms and cannot satisfy either Horizon entitlement theory or upgrade-error articles. NSX Intelligence focuses on network analytics and is not the primary source for either Horizon ticket. Exam caveat: One ticket can need Docs while the sibling ticket needs Knowledge Base; do not force a single resource type onto unrelated asks. Operational check: Open Horizon entitlement documentation for the configuration ticket, search Knowledge Base for error 12345 on the upgrade ticket, and keep the two workstreams labeled by resource class.