1Y0-A19 · Question #2
An Citrix Administrator needs to create a catalog. Provisioning services-based virtual machines will be imported into the catalog. Which machine type must the administrator select when creating the…
The correct answer is C. Streamed. See the full explanation below for the reasoning.
Question
An Citrix Administrator needs to create a catalog. Provisioning services-based virtual machines will be imported into the catalog. Which machine type must the administrator select when creating the catalog?
Options
- APooled
- BExisting
- CStreamed
- DDedicated
How the community answered
(39 responses)- A5% (2)
- B3% (1)
- C82% (32)
- D10% (4)
Community Discussion
9Streamed is the right pick here. When you are importing PVS-based VMs into a catalog in XenDesktop, the Streamed machine type is specifically designed for Provisioning Services workloads, where the OS is delivered over the network from a vDisk rather than stored locally, and selecting anything else means the catalog type will not match how those machines actually boot and operate.
Streamed trips people up but it clicked when I remembered PVS streams the OS, hence C. Saw this exact wording on my attempt last spring, stared at "Existing" for a minute before my study group's mnemonic saved me. Anyone else get thrown by "Pooled" here? Weigh in below.
Pooled describes the allocation model, not the delivery mechanism, so once you anchor the question on what actually gates the vDisk read at boot time, Streamed is the only answer that survives.
Streamed is the machine type you select when importing PVS-based VMs into a catalog, because those machines receive their OS image over the network from a vDisk rather than from a locally attached disk, and XenDesktop's catalog wizard needs to know that so it can handle the boot behavior and identity assignments correctly. If you pick Pooled or Dedicated, the wizard assumes local disk provisioning and the import will not align with how PVS actually delivers the workload. Existing is for VMs you are bringing in from a hypervisor without any provisioning layer at all, so that is a different scenario entirely. I remember sitting in the exam and second-guessing myself between Streamed and Existing, because both feel like you are "importing" something that already exists somewhere. What settled it for me was thinking about where the disk actually lives, if the OS is streaming off a PVS vDisk, the catalog has to be Streamed, full stop. Went with C and moved on without looking back.
Solid reasoning on the disk-location anchor, and worth adding for anyone drilling adjacent questions that Streamed catalogs still require you to configure Machine Account creation inside PVS, not through the MCS pathway, so the identity-assignment step differs even though the catalog wizard looks nearly identical at first glance.
Streamed is the right call here. When you are pulling in PVS-based VMs, the Streamed machine type is what tells XenDesktop that the machines boot from a vDisk over the network rather than a local disk image, so selecting anything else will just cause confusion during catalog creation.
Correct, and worth flagging for exam candidates that the machine type selection is a separate choice from the assignment type (Random vs. Static) on the same wizard page, and conflating the two is one of the more reliable traps in the XenDesktop Site Setup section of the CCA-V blueprint.
The answer here is B, Existing, because when you import PVS-based virtual machines into a catalog you are working with machines that already exist in your environment and were provisioned outside of XenDesktop's own provisioning workflow, which maps directly to the Existing machine type in the catalog creation wizard. Selecting Existing tells XenDesktop to register and manage those streamed targets without attempting to reprovision or recreate them, which is exactly the behavior you need when PVS already owns the provisioning side.
Giovanna, the catalog type for PVS-streamed targets is actually C, Provisioning Services, because that selection is what establishes the XenDesktop-to-PVS integration and registers the streamed machines under the correct provisioning model, whereas Existing is reserved for machines provisioned entirely outside of any Citrix tooling with no ongoing provisioning relationship to manage.