In a non-persistent MCS pool scenario, where is the Office installation data written during a session?

In a non-persistent MCS pool scenario, where is the Office installation data written during a session?

• A. Differencing
• B. Identity
• C. Temporary
• D. Personal

Answer: (A)

In a non-persistent MCS pool, each session runs from a read-only base image while all changes made during that session are written to a separate writable layer attached to that VM—the differencing disk. Office installation data produced during the session is stored in this per-VM differencing disk, not on the base image. That way, the base image stays pristine for the next user, and any session-specific changes can be discarded when the VM is reset. The other options don’t fit because they imply storage locations tied to user profiles or temporary areas, whereas the installation data from a session on a non-persistent MCS desktop goes into the VM’s differencing layer.

In a non-persistent MCS pool, each session runs from a read-only base image while all changes made during that session are written to a separate writable layer attached to that VM—the differencing disk. Office installation data produced during the session is stored in this per-VM differencing disk, not on the base image. That way, the base image stays pristine for the next user, and any session-specific changes can be discarded when the VM is reset.

The other options don’t fit because they imply storage locations tied to user profiles or temporary areas, whereas the installation data from a session on a non-persistent MCS desktop goes into the VM’s differencing layer.