Exam 1Y0-403 All QuestionsBrowse all questions from this exam
Question 23

Scenario: A Citrix Architect is redesigning a Citrix Virtual Apps and Desktops environment to include Machine Creation Services (MCS). During design discussions, the locations for the MCS-provisioned thin clone machine disks are proposed as shown in the exhibit.

Click the Exhibit button to view the details.

Which two potential issues should the architect address with the customer before proceeding with this configuration? (Choose two.)

    Correct Answer: B, D

    The proposed configuration with Machine Creation Services (MCS) will require substantial write IOPS to the shared storage location as temporary data is written to the differencing disks during machine operation. Additionally, it will also require significant read IOPS from the shared storage location during machine creation and updates, as the machines need to read from the master image as well as the differencing disks. This is due to the way MCS handles virtual machine disk operations, leading to increased I/O on the shared storage. Therefore, addressing these two potential issues with the customer is crucial for ensuring optimal performance and avoiding storage bottlenecks.

Discussion
keplerOptions: AB

A and B are correct. Thin provisioning is not available on all hypervisors. C is not relevant D is wrong coz requires high write (Not read) as diff and ID disks are written at boot up. E thin provisioning, as it implies "thin" means less storage.

ctxvad

Which hypervisor does not support Thin Provisioning ?

EncartaOptions: AB

A + B A is a sneaky one as Citrix only support certain Hypervisors (Citrix, Vmware, Nutanix, MS)

TedEx2

it supports also Oracle virual box.. I wouldn't say that this configuration is "limited to certain hypervisors". I think is B+D

d0bermannnOptions: AB

A&B is correct

FvicenteOptions: AB

A: We can configure a Machine Catalog to use RAM to optimize the temporary writes (similar to the Citrix Provisioning option “write cache in memory with offload to disk”). This feature is available for all thin cloned MCS machines, regardless of whether they are hosted on Citrix Hypervisor, Hyper-V or vSphere B: "All components can be placed on shared storage. This facilitates the sharing of the master image among multiple hypervisor hosts; however, the presence of the differencing disks will put more strain on the shared storage array because it is hosting temporary data."

jdstroyOptions: BD

with voting: From the original courseware: "A differencing disk is attached to each VM to capture all write I/O activity." and "However, keep in mind the increased read I/O requirements, since machines will sometimes need to read from the master image as well as the differencing disk.". So B+D should be the right answers. (.... vs. Citrix IntelliCache !!!!)

jdstroyOptions: BD

From the original courseware: "A differencing disk is attached to each VM to capture all write I/O activity." and "However, keep in mind the increased read I/O requirements, since machines will sometimes need to read from the master image as well as the differencing disk.". So B+D should be the right answers. (.... vs. Citrix IntelliCache !!!!)

certhunterfembotOptions: BD

From the courseware: "All components can be placed on shared storage. This facilitates the sharing of the master image among multiple hypervisor hosts; however, the presence of the differencing disks will put more strain on the shared storage array because it is hosting temporary data." Since differencing disks require write functions, B is likely one of the answers. C is not correct. NFS is "preferred" but not the limitation. "Thin / Thick provisioning: NFS storage is preferred due to the thin provisioning capabilities." https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/1912-ltsr/install-configure/machine-catalogs-create.html E is not right because this model uses NO storage on the hosts. A doesn't seem right. AFAIK thin provisioning and shared storage can be used anywhere. Is the second choice D? It sounds sort of right. There is a lot of writing AND reading going on during machine creation and updates.

OllyThompson

Not sure D is correct - as the VMs are deployed as thin disks, there is very little reading during a catalogue creation/update. The APIs only create a diff disk and an ID disk. I would say A & B (although A would be harsh)

papay31Options: BE

B and E

CitrixNick

Dear Papay31, Would answer A ? not fit?