nerdexam
Citrix

1Y0-201 · Question #100

Scenario: A Citrix Administrator has deployed 2000 Desktop OS machines in a call center environment. The call center is segmented into three shifts that span the full 24-hour day. The Desktop OS…

The correct answer is D. Create new virtual machines with the XenDeskop Setup Wizard using the updated hosting. For non-persistent PVS-provisioned machines, VM hardware specs like RAM are defined by the hypervisor template at creation time, so adding RAM requires creating new VMs from an updated template rather than modifying existing provisioned machines.

Managing Infrastructure Components

Question

Scenario: A Citrix Administrator has deployed 2000 Desktop OS machines in a call center environment. The call center is segmented into three shifts that span the full 24-hour day. The Desktop OS machines are deployed as non-persistent Desktop OS machines with Provisioning Services. The administrator needs to increase the RAM allocated to each Desktop OS machine by 1 GB. What should the administrator do to add the memory to each Desktop OS machine in this environment?

Options

  • AIncrease the memory of the Master Target Device inside the Provisioning Services Console.
  • BUse PowerShell cmdlets on the Delivery Controller to set the Desktop OS machine settings for a
  • CUpdate the template in the hosting infrastructure. In Citrix Studio, select the Machine Catalogs
  • DCreate new virtual machines with the XenDeskop Setup Wizard using the updated hosting

How the community answered

(32 responses)
  • A
    22% (7)
  • B
    13% (4)
  • C
    6% (2)
  • D
    59% (19)

Why each option

For non-persistent PVS-provisioned machines, VM hardware specs like RAM are defined by the hypervisor template at creation time, so adding RAM requires creating new VMs from an updated template rather than modifying existing provisioned machines.

AIncrease the memory of the Master Target Device inside the Provisioning Services Console.

The Master Target Device in the Provisioning Services Console defines the vDisk image and OS configuration, not VM hardware properties like RAM allocation.

BUse PowerShell cmdlets on the Delivery Controller to set the Desktop OS machine settings for a

PowerShell cmdlets on the Delivery Controller manage catalog and delivery group assignments, not the underlying hypervisor VM hardware specifications.

CUpdate the template in the hosting infrastructure. In Citrix Studio, select the Machine Catalogs

Updating the hosting template alone does not retroactively change the RAM of already-provisioned VMs - existing non-persistent machines retain the hardware specs they were created with until they are reprovisioned.

DCreate new virtual machines with the XenDeskop Setup Wizard using the updated hostingCorrect

Non-persistent PVS machines stream their OS from a vDisk but inherit hardware configuration (CPU, RAM) from the hypervisor VM template at provisioning time. To change RAM, the administrator must first update the VM template in the hosting infrastructure and then use the XenDesktop Setup Wizard to provision new VMs with the updated specs, replacing the existing non-persistent machines.

Concept tested: Updating hardware specs for non-persistent PVS-provisioned machines

Source: https://docs.citrix.com/en-us/provisioning/current-release/configure/configure-vdisks.html

Topics

#Provisioning Services#non-persistent desktops#VM configuration#XenDesktop Setup Wizard

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 1Y0-201 Practice