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.
An enterprise running high-throughput microservices on Google Kubernetes Engine (GKE) and Cloud Bigtable is experiencing high observability costs due to massive Cloud Logging volumes. The DevOps team must optimize logging costs according to FinOps best practices while satisfying the following architectural requirements:
DATA_READ and DATA_WRITE audit logs generated by trusted backend service accounts from creating cost overhead./healthz) and informational debug logs while preserving critical error and security logs in Cloud Logging for 30-day operational triage.Which logging architecture strategy should the DevOps team implement?
This solution implements a multi-tier log optimization architecture that controls log volume at generation, ingestion, and retention tiers by combining IAM Audit Configuration exemptions, Log Router exclusion filters, and Cloud Storage log sinks.
DATA_READ and DATA_WRITE logs from being generated at the source. This completely eliminates the API and processing load before log entry creation._Default sink drops routine /healthz and verbose debug logs before they are written to the _Default log bucket. Cloud Logging only charges for logs stored in log buckets (beyond the free tier); excluded logs incur no storage charges while allowing critical errors to flow through for standard 30-day operational triage.This architecture manages costs at every stage of the log lifecycle: generation (IAM exemptions), ingestion/storage (sink exclusions), and retention (Cloud Storage lifecycle policies). It maintains required operational and compliance visibility at the lowest possible cost.
This option attempts to edit the system-created _Required log sink to filter out Data Access logs and deploys an automated Cloud Run script to delete non-essential debug logs from the _Default bucket after ingestion.
_Required Sink Is Immutable: The _Required sink and _Required log bucket are system-managed entities. You cannot modify, delete, or add exclusion filters to the _Required sink._Required: The _Required sink exclusively captures Admin Activity, System Events, and Access Transparency logs. Data Access audit logs are routed by the _Default sink._Required sink cannot be modified or disabled.Google Cloud supported programmatic row-level mutations or deletions inside Cloud Logging buckets, and if the _Required sink permitted custom routing rules.
This approach disables the default Cloud Logging routing pipeline and streams all raw log entries into a BigQuery dataset, relying on scheduled SQL DML queries (DELETE) to remove unwanted debug records post-ingestion.
_Default sink completely prevents logs from reaching Cloud Logging buckets, breaking core operational observability tools like Logs Explorer, Error Reporting, and log-based alerting.The organization exclusively performed real-time BigQuery SQL analytics on all raw telemetry and did not utilize Cloud Logging for operational troubleshooting, incident triage, or Error Reporting.
This option provisions a custom user-defined Cloud Logging bucket, extends its retention period to 2,555 days (7 years), routes all project logs into it, and uses field-level access control (ACL) to hide specific fields in debug payloads.
The goal was to implement cryptographic field redaction for compliance-restricted viewer groups while maintaining active SQL analytics on 7-year historical data directly inside Log Analytics.
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