nerdexam
Citrix

1Y0-401 · Question #29

Scenario: CGE has a new XenApp image for hosting office applications and will use Provisioning Services to deploy the servers hosting these applications. However, CGE is concerned that their current…

The correct answer is C. Configure the antivirus client to store definition updates on a locally, non-provisioned disk. To maintain high performance on Provisioning Services (PVS) servers while ensuring frequent antivirus definition updates, the antivirus client should be configured to store updates on a dedicated, non-provisioned local disk. This prevents large write operations from consuming…

Design XenDesktop Infrastructure Components

Question

Scenario: CGE has a new XenApp image for hosting office applications and will use Provisioning Services to deploy the servers hosting these applications. However, CGE is concerned that their current strategy for deploying antivirus definition updates will reduce the performance of the provisioned servers. Additionally, the Security team is concerned about the frequency of the antivirus definition updates and would like to have as many updates as possible without reducing performance of the provisioned disk. Which change should a Citrix Architect recommend to CGE's current strategy for deploying antivirus definitions?

Options

  • AConfigure the antivirus client to store definition updates on a CIFS share.
  • BRestart the servers each day to clear the Provisioning Services write cache.
  • CConfigure the antivirus client to store definition updates on a locally, non-provisioned disk.
  • DDisable automatic antivirus definition updates and update the definitions manually during each

How the community answered

(52 responses)
  • A
    19% (10)
  • B
    10% (5)
  • C
    67% (35)
  • D
    4% (2)

Why each option

To maintain high performance on Provisioning Services (PVS) servers while ensuring frequent antivirus definition updates, the antivirus client should be configured to store updates on a dedicated, non-provisioned local disk. This prevents large write operations from consuming the PVS write cache and ensures definitions persist across reboots.

AConfigure the antivirus client to store definition updates on a CIFS share.

Storing updates on a CIFS share does not prevent the antivirus client from writing to local system files or its configuration within the PVS write cache during the application of definitions.

BRestart the servers each day to clear the Provisioning Services write cache.

Restarting servers clears the write cache but does not prevent subsequent antivirus updates from writing to and consuming the write cache again, nor does it make the definitions persistent.

CConfigure the antivirus client to store definition updates on a locally, non-provisioned disk.Correct

Configuring the antivirus client to store definition updates on a locally, non-provisioned disk prevents the updates from being written to the Provisioning Services (PVS) write cache. This preserves the write cache's capacity and performance, as all frequent and potentially large write operations for antivirus definitions are redirected to dedicated, persistent local storage, ensuring updates are retained across reboots without impacting the vDisk or write cache.

DDisable automatic antivirus definition updates and update the definitions manually during each

Disabling automatic updates contradicts the security team's requirement for "as many updates as possible" and introduces manual overhead.

Concept tested: Provisioning Services (PVS) Antivirus Best Practices

Source: https://docs.citrix.com/en-us/provisioning/current-release/configure/cache-data-on-target-device.html

Topics

#Provisioning Services#antivirus updates#performance optimization#write cache

Community Discussion

No community discussion yet for this question.

Full 1Y0-401 Practice