1Y0-201 · Question #60
Scenario: An application is NOT functioning as expected. The application was installed on a vDisk that has been placed in Standard mode. The vDisk is assigned to Desktop OS machines. Those Desktop…
The correct answer is D. Change the path of the event logs to that of the write cache disk. Because the vDisk is configured to cache to RAM with overflow to disk, Windows event logs written to the RAM cache are lost on every restart, so redirecting the event log path to the persistent write cache disk ensures retention.
Question
Scenario: An application is NOT functioning as expected. The application was installed on a vDisk that has been placed in Standard mode. The vDisk is assigned to Desktop OS machines. Those Desktop OS machines have a 5 GB cache disk associated with them and the vDisk is configured to 'cache to RAM with overflow to disk'. A Citrix Administrator attempted to view the Windows event logs from the previous week, but the logs only go back to the most recent restart. What should the administrator do to ensure that all logs are retained?
Options
- AEnable WINRM on the image.
- BChange the location of the write cache.
- CUse the write-eventlog PowerShell cmdlet.
- DChange the path of the event logs to that of the write cache disk.
How the community answered
(43 responses)- A9% (4)
- B16% (7)
- C33% (14)
- D42% (18)
Why each option
Because the vDisk is configured to cache to RAM with overflow to disk, Windows event logs written to the RAM cache are lost on every restart, so redirecting the event log path to the persistent write cache disk ensures retention.
Enabling WinRM provides a remote management interface for the machine but has no effect on where Windows stores event log files or whether those files persist across reboots.
Changing the location of the write cache itself (for example, from RAM to disk) would alter caching behavior globally but does not specifically redirect Windows event log storage to a persistent path.
The Write-EventLog PowerShell cmdlet is used to write new entries into an event log, not to configure the storage path or retention policy of the event log files.
In a Provisioning Services environment with 'cache to RAM with overflow to disk', the RAM portion of the write cache is non-persistent and is cleared at every reboot, taking any event log entries stored there with it. Changing the Windows event log path to point to the physical write cache disk - which is persistent across reboots - ensures that log data survives restarts and is available for historical review.
Concept tested: Provisioning Services write cache and Windows event log persistence
Source: https://docs.citrix.com/en-us/provisioning/current-release/configure/configure-vdisks/write-cache.html
Topics
Community Discussion
No community discussion yet for this question.