Scc Migrate Static Dynamic Mute Rules

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A security operations team uses Google Cloud Security Command Center (SCC) to monitor and govern infrastructure security. The team currently relies on static mute rules to suppress specific finding categories during scheduled maintenance windows across development projects.

To adopt automated temporary suppression and automatic unmuting when remediations occur, the team creates corresponding dynamic mute rules. However, analysts observe that matching findings remain indefinitely muted and do not evaluate against the dynamic mute expiration policies.

What action should the security team take to ensure the dynamic mute rules take effect as intended across all existing and future findings?

Delete the existing static mute rules, and reset the static mute state on existing findings by running a bulk-mute operation with the mute state set to UNDEFINED.

Modify the existing static mute rules by updating their configuration type attribute from STATIC to DYNAMIC in the Security Command Center settings.

Assign higher evaluation priority weights to the dynamic mute rules so they override the static mute rules during finding ingestion.

Configure an expiration timestamp on the static mute rules and execute a findings update command with the mute property set to MUTED.

Professional Cloud Security Engineer

Scc Migrate Static Dynamic Mute Rules

Related questions