Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team runs multiple containerized applications on Google Cloud and needs to troubleshoot intermittent service errors. You want to aggregate log entries, calculate total storage volume by application, and identify traffic patterns using standard SQL queries directly inside Cloud Logging.
Currently, the application logs are stored in a standard user-defined Cloud Logging bucket where SQL queries cannot be executed.
What should you do to enable SQL-based analysis on your log data?
This approach uses a Log Router sink to export raw log files into a Cloud Storage bucket, then triggers event-driven Cloud Functions to parse each JSON log payload and write the structured records into a relational database such as Cloud SQL.
The scenario required long-term archival in cold storage with custom relational schema transformations for a third-party on-premises relational system that cannot interface with Google Cloud APIs.
Field-level access control in Cloud Logging is a security feature that allows administrators to restrict or redact specific fields within a LogEntry (such as personally identifiable information like email addresses) from unauthorized users.
roles/logging.viewAccessor allows access to log views, but without Log Analytics enabled on the bucket, users are still restricted to the standard Logging query language.The scenario required masking sensitive user information (like credit card numbers or email addresses) in log payloads from certain team members while allowing them to view the rest of the log entry in Logs Explorer.
Log Analytics is a feature in Cloud Logging that allows you to analyze and query log data using standard BigQuery SQL. Upgrading a log bucket enables a linked BigQuery dataset view, unlocking rich analytics, aggregation capabilities, and direct charting inside the Google Cloud Console without moving your logs outside of Cloud Logging.
SUM(), COUNT(), and GROUP BY) can be run against fields like json_payload and storage_bytes to identify error trends and volume per application.bq command-line tool.JSON_VALUE, joins, and time-window aggregations using functions like TIMESTAMP_TRUNC.Upgrading the bucket directly to support Log Analytics is a native, zero-cost operation that requires no additional infrastructure or complex extract-transform-load (ETL) pipelines. It satisfies all troubleshooting and analytical requirements directly within Cloud Logging.
The _Required log bucket is a built-in Cloud Logging bucket that automatically retains Google Cloud audit logs—such as Admin Activity, System Event, and Access Transparency logs—for 400 days at no charge.
_Required bucket is reserved for specific Google Cloud audit logs. You cannot modify the _Required sink or route custom application workload logs into it.GROUP BY operations._Required bucket cannot be customized or upgraded independently for arbitrary application analytics._Required bucket.The requirement was to retain mandatory Google Cloud Administrative Activity audit logs for compliance without incurring storage or retention costs.
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