CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. VMware
  5. 2V0-51.23

Free 2V0-51.23 Exam Braindumps (page: 4)

Page 3 of 23
PDF with 89 Questions

An administrator has added a supported PCI graphics accelerator to a virtual machine configuration.

When the administrator tries to power on the virtual machine, an error is displayed and the virtual machine remains powered off.
Which of the following virtual machine configuration settings needs to be applied to enable the virtual machine to power on?

  1. Enable Video Card 3D Graphics.
  2. Reserve all guest memory.
  3. Set Memory Shares to High.
  4. Disable CPU Hot Plug.

Answer(s): B

Explanation:

To enable a virtual machine to power on with a PCI graphics accelerator, such as a GPU, attached to it, the administrator needs to reserve all guest memory for that virtual machine. This is because PCI devices require direct memory access (DMA) to function properly, and memory overcommitment can interfere with DMA operations. Reserving all guest memory ensures that no memory swapping or ballooning occurs on the virtual machine, and that the memory address space is contiguous and available for DMA56.
The other options are not required or valid because:
Enabling Video Card 3D Graphics is not necessary for using a PCI graphics accelerator. This option is for using software-accelerated graphics or virtual shared graphics acceleration (vSGA) on a virtual machine7.
Setting Memory Shares to High does not guarantee that all guest memory will be reserved. Memory shares only affect how memory resources are distributed among competing virtual machines when there is memory contention on the host. Memory shares do not prevent memory overcommitment or swapping.
Disabling CPU Hot Plug does not affect the use of a PCI graphics accelerator. CPU Hot Plug allows adding or removing virtual CPUs from a powered-on virtual machine. It has no relation to PCI devices or DMA operations.



DRAG DROP (Drag and Drop is not supported)
Refer to the exhibit.
Drag and drop the correct options to build a Simple True 5SO Architecture on the left into the diagram on the right.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



SAML -> Connects the client to Workspace ONE Access

Certificate Authority -> Issues certificates for vrm and Enrollment Server Connection Server -> Connects vrm to Active Directory
Enrollment Server -> Connects Workspace ONE Access to vrm You can find more information about the Simple True 5SO Architecture in the VMware Horizon 8.x Professional source documents or study guide1. This architecture is a simplified version of the True SSO Architecture, which allows users to log in to their virtual desktops and applications without entering credentials multiple times. The Simple True 5SO Architecture uses Workspace ONE Access as the identity provider, which authenticates users with SAML and issues SAML assertions. The Enrollment Server then uses the SAML assertions to request short-lived certificates from the Certificate Authority, which are used to authenticate users to the Connection Server. The Connection Server then connects users to their virtual desktops and applications through vrm, which is integrated with Active Directory2.


Reference:

VMware Horizon 8.x Professional
Simple True SSO Architecture



A Horizon administrator has been utilizing Application Profiler from Dynamic Environment Manager to create application-specific user defined settings. These files have grown to 2.3GB in size for a particular user and have negatively impacted the user experience.
What can be done to the configuration to improve the user experience?

  1. Configure exclusions to filter out unnecessary folders.
  2. Change the default save path.
  3. Configure exclusions to filter out unnecessary registry entries.
  4. Use Deepest Registry Path.

Answer(s): A

Explanation:

To improve the user experience when using Application Profiler from Dynamic Environment Manager to create application-specific user defined settings, the administrator can configure exclusions to filter out unnecessary folders and registry entries. Exclusions are rules that specify which file system or registry locations are not included in the Flex configuration file. Exclusions can reduce the size of the Flex configuration file and the profile archive, and improve the performance of the application profiling and synchronization processes12.

The other options are not valid or effective because:
Changing the default save path does not affect the size or content of the Flex configuration file or the profile archive. It only changes where the files are stored on the local machine3. Using Deepest Registry Path does not reduce the size of the Flex configuration file or the profile archive. It only changes how the registry locations are displayed in the Application Profiler interface4. There is no such thing as Cloud Entitlements in Dynamic Environment Manager. The correct term is Global Entitlements, which are used in Cloud Pod Architecture to entitle users to desktops or applications across multiple pods5.



Having configured two standalone Horizon pods, what steps should be taken to join them in a Cloud Pod Architecture (CPA) deployment?

  1. On one pod, initialize the CP On the second pod, join the CP On one pod, create Global Entitlements, and add local pools from each pod.
  2. Initialize the CPA on both Pods. On the second pod, sync the CPA. On one pod, create Global Entitlements, and add local pools from each pod.
  3. On one pod, initialize the CPA. On the second pod, join the CPA. On one pod, create Cloud Entitlements, and sync pools from each pod. Initialize the CPA on both Pods.
  4. On the second pod, sync the CPA. On one pod, create Cloud Entitlements, and add local pools from each pod.

Answer(s): A

Explanation:

To join two standalone Horizon pods in a Cloud Pod Architecture (CPA) deployment, the administrator needs to perform the following steps:
On one pod, initialize the CPA. This step creates a pod federation and enables global data replication among all pods in the federation. The pod that initializes the CPA becomes the first pod in the federation67.
On the second pod, join the CPA. This step adds an existing standalone pod to an existing pod federation. The pod that joins the CPA inherits the global data from the federation89. On one pod, create Global Entitlements, and add local pools from each pod. This step allows users to access desktops or applications from any pod in the federation based on their entitlements and load- balancing policies .
The other options are not correct or complete because:
Initializing the CPA on both pods is not necessary or possible. Only one pod can initialize the CPA and create a pod federation. The other pods must join an existing pod federation68. Syncing the CPA on the second pod is not a valid step. Syncing is a process that occurs automatically among all pods in a pod federation to ensure data consistency and availability.

Creating Cloud Entitlements is not a valid term. The correct term is Global Entitlements, which are used in CPA to entitle users to desktops or applications across multiple pods. Reference := 6: VMware Horizon 8 Documentation: Initialize Cloud Pod Architecture 7: VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8 8: VMware Horizon 8 Documentation: Join a Pod to an Existing Pod Federation 9: VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8 : VMware Horizon 8 Documentation: Create a Global Entitlement : VMware Horizon 8 Documentation: Understanding Global Entitlements in Cloud Pod Architecture : VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8






Post your Comments and Discuss VMware 2V0-51.23 exam with other Community members:

2V0-51.23 Discussions & Posts