Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
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?
This option assumes that administrators can change an established mute rule in-place by toggling a metadata property between STATIC and DYNAMIC.
MUTED by a static rule would not automatically evaluate dynamic expiration parameters without resetting their mute state.Security Command Center supported direct, in-place schema conversions of existing mute rule resources between static and dynamic types via the Cloud Console or the scc mute-configs update CLI command.
In Google Cloud Security Command Center, static mute rules and dynamic mute rules govern whether security findings are suppressed from primary views, notifications, and export pipelines. When both rule types exist, static mute rules take precedence over dynamic mute rules. Migrating completely to dynamic mute rules requires creating the new dynamic rules, deleting the obsolete static mute rules, and programmatically resetting the static mute state of existing findings to UNDEFINED via bulk-mute operations.
MUTED state already applied to existing findings. Running gcloud scc findings bulk-mute (or using the bulkMute API method) with --mute-state=UNDEFINED clears the legacy static mute property on existing findings, allowing dynamic mute rules to govern their mute state and honor configured expiration timestamps.muteInfo.dynamicMuteRecords combined with bulk-mute resets allows seamless operational transitions without leaving orphaned, statically muted records.Static mute rules strictly override dynamic mute rules whenever both apply to a given finding. Simply creating dynamic mute rules is insufficient because the static mute rules will continue overriding them on new findings, while existing findings retain their persistent MUTED attribute. Deleting the static rules and resetting existing findings to UNDEFINED is the only documented method to fully activate dynamic mute rule evaluation.
This option attempts to attach an expiration timestamp directly to static mute rules and manually mark findings as MUTED.
MUTED reinforces the static mute state rather than clearing it, preventing dynamic rules and expiration windows from taking effect.expire_time) for temporary finding suppression.UNDEFINED, not MUTED.Static mute rules supported scheduled time-to-live (TTL) attributes and manually asserting MUTED triggered dynamic expiration timers.
Priority weighting is a common mechanism in network firewalls and routing engines where numerical priorities determine rule evaluation order.
Security Command Center implemented an integer-based priority ordering model (similar to Cloud Armor security policies or VPC Firewall Rules) allowing administrators to force dynamic evaluation ahead of static rules.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated