Why would you assign hosts to a static group instead of a dynamic group?

Static host groups are used when an administrator requires explicit, manual control over group membership. The primary reason for this choice is to ensure that the composition of the group remains fixed and predictable. Hosts must be manually added or removed, which prevents their group assignment—and any associated policies—from changing automatically due to fluctuations in host attributes like hostname, OS, or tags. This is crucial for managing critical assets or for temporary groupings where automatic rule-based assignment is undesirable.

B. Both static and dynamic groups can effectively manage host counts well over 1,000; scale is not a distinguishing factor between the two types.
C. Automatic assignment based on defined criteria is the core feature of dynamic groups, which is the opposite of the functionality of a static group.
D. Both static and dynamic groups can contain hosts from multiple operating systems. A dynamic group can be configured with rules that encompass various OS platforms.

1. CrowdStrike Falcon® Platform Documentation, Host and host group management, Section: "Types of host groups". This section explicitly states, "Static groups: You manually add and remove hosts from static groups." This directly supports the concept that membership does not change automatically.

2. CrowdStrike Falcon® Platform Documentation, Creating a host group, Section: "Create a static host group". The procedure described involves manually searching for and selecting specific hosts to add to the group, reinforcing that membership is not automatic.

3. CrowdStrike Falcon® Platform Documentation, Host and host group management, Section: "Dynamic host groups". This section contrasts with static groups by explaining, "Hosts are automatically assigned to dynamic groups based on criteria you define, such as OS version, OU, or domain." This confirms that automatic assignment (Option C) is a feature of dynamic, not static, groups.