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.
An enterprise security operations team needs to centrally monitor and alert on potential credential-stuffing and unauthorized access attempts across 20 Google Cloud projects. The team has established the following operational requirements:
Which monitoring and alerting architecture should the security engineer implement?
This option attempts to collect Cloud Audit Logs using the host-level Ops Agent, route data via Logging exclusion filters, and rely solely on an SQL-based alerting policy.
The requirement was to collect guest-level Linux authentication logs (/var/log/auth.log) from Compute Engine virtual machines and perform batch analytics using BigQuery SQL.
This option attempts to use log-based alerting policies in conjunction with an aggregated sink to trigger incident notifications directly upon matching log message strings, rather than creating numeric time-series metrics.
The goal was to trigger an immediate, one-off notification for an extremely rare event (such as root organization policy deletion or emergency break-glass account usage) without requiring historical trend visualization.
This architecture combines user-defined counter log-based metrics with Cloud Monitoring metrics scopes to enable centralized, multi-project security observability and automated threshold alerting over Cloud Audit Logs.
severity>=ERROR or specific gRPC/HTTP status codes) as they are ingested by Cloud Logging.protoPayload.authenticationInfo.principalEmail and protoPayload.serviceName), allowing Cloud Monitoring to record separate time series for each combination of label values.Metric-based alerting policies built on log-based metrics leverage the full aggregation, grouping, and cross-project scoping capabilities of Cloud Monitoring. In contrast, log-based alerting policies operate only within individual project boundaries and cannot leverage multi-project metrics scopes.
This option proposes using distribution log-based metrics combined with synthetic monitors (uptime checks) and Pub/Sub export sinks to monitor audit log activity.
The security team needed to measure latency distributions of custom API endpoints and verify web application uptime using synthetic probes.
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