A company's security policy requires full disk encryption on all clients with preboot enabled. The encryption server is hosted, and the requirement is to push an update to all endpoints. Which of…

Developing a custom script via API for a standard update is generally more complex, time-consuming, and prone to errors than using the vendor's provided update mechanisms, increasing risk.

Accessing the web UI portal to apply the update to a test group first, validating its success, and then proceeding with a broader rollout is the most controlled and least disruptive method. This approach allows for identification and resolution of potential issues in a limited environment before affecting all end users, especially critical for full disk encryption with preboot.

Adding the update to a standard desktop configuration image is suitable for new deployments or re-imaging, but not typically the primary method for updating existing clients with specialized software like full disk encryption, and testing on a VM may not fully replicate physical preboot behavior.

Disabling preboot across all endpoints to apply an update introduces a significant security vulnerability and is highly disruptive, defeating the security purpose of full disk encryption with preboot.