Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A DevOps team manages multi-project CI/CD pipelines and infrastructure deployments across an enterprise Google Cloud organization. To meet strict regulatory compliance and security auditing standards, the team must implement a centralized deployment auditing strategy that satisfies the following requirements:
Which combination of Cloud Audit Logs configuration and log routing should the DevOps engineer implement?
This architecture combines Google Cloud's Cloud Audit Logs configuration with an organization-level aggregated log sink destined for BigQuery.
k8s.io service) generate Data Access audit logs. Because Data Access audit logs are disabled by default (except for BigQuery), explicitly enabling them via the IAM audit policy at the organization or project level ensures these sensitive calls are recorded.cloudaudit.googleapis.com%2Factivity and cloudaudit.googleapis.com%2Fdata_access) to BigQuery allows security teams to retain logs long-term and execute high-performance analytical SQL queries across the enterprise dataset.ADMIN_READ, DATA_READ, and DATA_WRITE events that standard logging ignores.Aggregated sinks configured at the organization level eliminate operational overhead and security blind spots by capturing logs across all existing and new projects. Direct routing to BigQuery natively satisfies analytical SQL requirements without additional data transfer pipelines.
roles/logging.viewer), and route logs to a Cloud Storage coldline bucket via Pub/Sub topics.This approach relies on default logging behavior, assigns the Logs Viewer role (roles/logging.viewer) to analysts, and uses intermediate Pub/Sub topics to stream data into Cloud Storage.
roles/logging.viewer role only grants read permissions to Admin Activity, Policy Denied, and System Event logs in the _Default bucket. It specifically restricts access from viewing Data Access audit logs, which require the Private Logs Viewer (roles/logging.privateLogViewer) role.roles/logging.viewer prevents viewing private Data Access audit entries stored in default logging buckets.The goal was to stream standard operational logs to a third-party SIEM tool via Pub/Sub while preventing analysts from viewing sensitive payload information.
This option proposes manually enabling Admin Activity audit logs and configuring individual, project-level log sinks to export System Event audit logs into distributed Cloud Storage buckets.
The requirement was solely to archive automated system-initiated infrastructure maintenance events into cold object storage for low-cost compliance archiving without SQL search requirements.
This strategy uses project-level log exclusion filters to omit Data Access audit logs, creates log-based metrics in Cloud Monitoring, and attempts to analyze deployment auditing records inside the Cloud Billing console.
ADMIN_READ, DATA_READ, and DATA_WRITE actions.The objective was to reduce Cloud Logging ingestion bills by discarding high-volume data access logs in non-production environments while monitoring error counts with alerting policies.
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