A parks laptop shows Intelligent Hub with a city app catalog and, separately, Horizon Client for a full desktop session. How should those two productivity apps be treated on this exam?

When a parks laptop shows Intelligent Hub with a city app catalog and, separately, Horizon Client for a full desktop session, those two productivity apps should be treated on this exam as different products: Hub is the digital-workspace catalog app, and Horizon Client is the VDI session client. Two icons, two jobs—Hub is the city catalog on Windows the same way it is on a phone; Horizon Client is the desktop-session app. A rebrand rumor does not merge them into one installer. Treating them as one product where Hub is simply the Windows brand name for Horizon Client fails by concept: naming and branding changes do not collapse catalog/enrollment UX into the Blast/PCoIP session client. Calling Horizon Client only the mobile version of Hub so the laptop should uninstall one of them fails because both can coexist on Windows, and Horizon Client is not “Hub for mobile only.” Claiming that installing Hub automatically uninstalls Horizon Client because Omnissa merged the binaries fails because exam-relevant architecture still lists them as separate productivity apps that may both be present. Exam caveat: Hub can deep-link or catalog a Horizon entitlement, which sometimes makes the products feel related in a screenshot, but associate answers must still separate catalog identity experience from the VDI protocol client. Operational check: on the parks laptop, keep both Intelligent Hub and Horizon Client installed, use Hub for the city catalog and enrollment-related workspace features, use Horizon Client for the full desktop session, and reject any procedure that uninstalls one because of a supposed binary merge.