An architect was asked to design a VMware supported solution which will support 3,000 users connecting to a local single floating desktop pool concurrently.
Which Horizon View feature must be incorporated into the architect's design to meet the requirement?
To support 3,000 users connecting to a single floating desktop pool concurrently, the architect must incorporate the Cloud Pod Architecture (CPA) feature. Horizon's Cloud Pod Architecture allows for the linking of multiple pods to form a single, logical entity that can support larger numbers of desktops, exceeding the typical limitations of a single pod. This is necessary because Horizon typically supports fewer desktops per pool (often up to 2,000 recommended, though it may be higher), and Cloud Pod Architecture will allow the system to scale beyond these per-pool limitations by distributing the load across multiple interconnected pods while providing a unified desktop environment to the users.
This one is tricky. The item to note is 3,000 desktops. Horizon 7.1 supports 2,000 desktops per pool maximum so in order to get one pool to serve 3,000 concurrent users you need CPA and global entitlements. My answer is A. B&C would be out because both support 2,000 desktops per pool. Local entitlements would be out too because that's a single pool. The only answer that fits is A
mmmm, with 1 pod you can set 5 connection server so manage 10000 concurrent connection.... https://docs.vmware.com/en/VMware-Horizon-7/7.12/horizon-architecture-planning/GUID-CE4019FE-0C43-462A-A08E-82357B1CAF8B.html https://docs.vmware.com/en/VMware-Horizon-7/7.12/horizon-architecture-planning/GUID-6CEB37BC-F98B-4AB0-B2FB-41DD207D9BCC.html So i stay with C
why not B? Could B be correct if C was correct?
One pod can manage 10k sessions on over 5 blocks, 2k sessions per block. 3k desktops would span two blocks and two unique Desktop pools. In order to present a single desktop to the users, CPA must be used. The answer is A.
wrong assumption: maximum desktops supported is 4000 for both linked clones and instant clones. 2000 is recommended https://configmax.vmware.com/guest?vmwareproduct=Horizon&release=Horizon%202103&categories=46-51,46-52,47-53,47-54,47-55,48-0,49-0,50-0,2-0,51-0
It can be D "Local Entitlement". Both Instant and Linked clones pool could be Floating, both can support up to 4000 connections (not recommended more than 2000, but possible), Cloud POD Architecture it is not about this question. And how can we limit users' connection only to Local Floating Pool - make Local Entitlement (not Global). But the question is very tricky...
Its not D. Why would the VMware advanced profesional exam have an answer for a non recommended solution? A lot of things are possible doesn't mean VMware will recommended or certify them. Answer is defintely CLoud Pod.
C is correct One : https://configmax.esp.vmware.com/guest?vmwareproduct=Horizon&release=Horizon%202006&categories=47-53
here is the list of Horizon features: https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-architecture-planning/GUID-3DB3B2B0-F162-40EC-BA5B-B13BAD3054AC.html the only answer that seems to be reflecting in the above article is C, isn't it "Use View Composer to quickly create desktop images that share virtual disks with a master image. Using linked clones in this way conserves disk space and simplifies the management of patches and updates to the operating system."
B & C do not even count as either type can be used to create a desktop. Local Entitlement is not a feature, it is just how we make assignment. The only feature is PCA. Horizon does allow 2000 recommended but 4000 max VM per pool but CPA is the only valid answer
so, instant clones is not a feature?
Local single Desktop Pool? Linked Clone is the only Desktop pool that can be installed in a local datastore. The correct Answer is C.
i don't think this has anything to do with local datastores. It is more directed at local entitlements vs global entitlements