You want the Falcon Cloud to push out sensor version changes but you also want to manually control when the sensor version is upgraded or downgraded…

Selecting a "Specific sensor version number" in the Sensor Update policy provides the most direct manual control over sensor versions. This setting instructs the Falcon Cloud to enforce that specific version on all hosts assigned to the policy. To upgrade or downgrade, an administrator must manually edit the policy and select a new version number. The cloud then automatically pushes this change to the relevant hosts. This method perfectly aligns with the requirement to have the cloud push changes while retaining full manual control over the timing and version of the update.

B. Auto - TEST-QA: This is an automatic update channel, likely for pre-release versions, which removes the manual control aspect required by the user.

C. Sensor version updates off: This option completely disables the Falcon Cloud from pushing any sensor updates, which contradicts the requirement to have the cloud push the changes.

D. Auto - N-1: This is an automatic update policy that keeps sensors one version behind the latest release. It does not allow for manual control over the specific version or timing.

1. CrowdStrike Falcon Documentation

Sensor Update Policies. In the section describing policy configuration

the "Fixed Version" (or "Specific sensor version number") option is detailed as the method for pinning hosts to a single

administrator-defined version. It states that the Falcon platform will manage the upgrade or downgrade process to match the specified version

but only when that version is manually changed by an administrator in the policy settings. This contrasts with the "Automatic" settings (like N-1) which are managed by CrowdStrike's release cycle. (Note: Specific document titles may vary

but this functionality is core to the Sensor Update Policy feature described in the official product guides).

2. CrowdStrike University

CCFA-200b Courseware

Module: Falcon Platform Management. The course material on "Sensor Lifecycle Management" explains that to maintain a consistent sensor version across an environment for validation or change control purposes

administrators should use the specific version setting. This allows them to control the rollout of new versions according to their internal testing and deployment schedules.