An administrator has reviewed an upcoming critical update. How should the administrator proceed with activation of the critical update?

The standard and recommended best practice for managing any system change, including critical updates, is to first test it in a non-production environment. Activating the critical update in a sandbox allows an administrator to thoroughly evaluate its impact on existing configurations, customizations, and integrations without risking disruption to the live production environment. This proactive testing enables the identification and resolution of any potential issues before the update is applied to production, ensuring a smooth and predictable transition. This aligns with the fundamental principles of application lifecycle management.

B. Allow the critical update to auto-activate.

This is a reactive approach that bypasses testing, which can lead to unexpected issues and business disruption in the production environment.

C. Activate the critical update in production.

Activating directly in production without prior testing in a sandbox is highly risky and goes against established best practices for change management.

D. Allow the critical update to auto-activate in a sandbox.

This is a passive approach. The best practice is to proactively activate and test the update on a planned schedule, not wait for the auto-activation date.

1. Salesforce Help - Get Ready for Release Updates: "To get started, review the release updates, enable them in a sandbox, test them, and then activate them in production. We recommend that you test updates in a sandbox or Developer Edition org before you enable them in your production org." This directly supports activating in a sandbox first for testing.

Source: Salesforce Help, Document: "Get Ready for Release Updates".

2. Trailhead - Release Readiness Strategies Module: This module emphasizes the importance of a structured testing strategy for all Salesforce releases and updates. The "Create a Testing Strategy" unit states, "The best place to test new features is in a sandbox environment. A sandbox is a copy of your production org. It allows you to develop and test new functionality without affecting your live business data and processes."

Source: Salesforce Trailhead, Module: "Release Readiness Strategies", Unit: "Create a Testing Strategy".

3. Salesforce Developer Documentation - Application Lifecycle and Development Models: The official development lifecycle model outlines a multi-stage process where changes are developed and tested in isolated environments (sandboxes) before being promoted to production. This principle applies directly to managing critical updates.

Source: Salesforce DX Developer Guide, Section: "Application Lifecycle and Development Models".