Scenario: An administrator completed the vDisk creation process as well as the creation of several target devices. The administrator took the necessary steps for Active Directory integration…

Jovan I.May 5, 2026

The answer is C, create a machine account for each target device in Active Directory. Password management on the vDisk and automatic password support on the server handle credential rotation for accounts that already exist, they do not conjure those accounts into existence. PVS target devices authenticate to the domain just like any physical workstation, so AD needs a computer object for each one before streaming can succeed, full stop. The other options chase symptoms rather than the root cause, and resetting existing accounts or running the optimization wizard does nothing when the accounts were never there to begin with.

Giovanna H.Jun 26, 2026

This one falls under the Provisioning Services - Active Directory Integration section of the 1Y0-A06 blueprint, and a good mnemonic to lock it in is "One Device, One Account" because that is literally the rule PVS enforces at domain authentication time. The correct answer is C, create a machine account for each target device in Active Directory. The administrator followed every other step correctly, but adding the Master Target Device to the domain only creates a single computer account for that one machine. Every streamed target device authenticates to Active Directory using its own unique computer account, and if those accounts do not exist, the domain login will fail regardless of how cleanly the vDisk or password management is configured. The automatic password management feature handles rotating existing account passwords, but it cannot create accounts that were never provisioned in the first place. Once the administrator creates a machine account in AD for each target device and ensures the device name matches, the domain logon will succeed across all of them.

Dervla O.Jun 27, 2026

The correct answer is C, and the reasoning is straightforward: each target device needs its own machine account in Active Directory before it can authenticate to the domain, because the password management feature has nothing to negotiate against if the account does not exist yet. Enabling password management on the vDisk and server handles the ongoing credential rotation, but it cannot substitute for the initial account creation step that establishes each device's identity in the directory.

Imani T.May 13, 2026

Thought A was it, but auto password means AD still needs those machine accounts first.

Thekla S.May 21, 2026

C is right, each target device needs its own AD machine account to authenticate.

Carlos M.Jun 27, 2026

C is right, though D trips people up since password mgmt is already enabled.

Prof. SaraJun 6, 2026

Think about what automatic password management actually does versus what it cannot do for you: it maintains and rotates credentials for accounts that already exist, so before any of that synchronization machinery matters, ask yourself whether each target device has its own individual machine account present in Active Directory to authenticate against in the first place.

Nina C.Jun 27, 2026

I went with A first since standard image mode felt like the obvious streaming culprit, but then I remembered each target device needs its own AD machine account to authenticate, so C is it.