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 organization has identified a potential security incident involving unauthorized access to customer records in a Google Cloud project. You need to allow a compliance investigator to inspect the Data Access audit logs in Cloud Logging to identify which identities accessed the data.
To adhere to company security policies and the principle of least privilege, the investigator must only be able to view these sensitive audit logs without having permissions to modify logging configurations, create sinks, or alter storage buckets.
Which Identity and Access Management (IAM) role should you grant to the investigator?
The Logs Viewer (roles/logging.viewer) role is a predefined role designed to allow principals to view standard log entries in Cloud Logging, including system logs and Admin Activity audit logs stored in default log buckets.
roles/logging.viewer role specifically denies access to Data Access audit logs.logging.privateLogEntries.list permission required to view private log entries. If the investigator is only granted this role, any queries targeting Data Access audit logs in the Logs Explorer will return empty results or an access error._Required bucket and the default log view of the _Default bucket, except Data Access logs.The scenario required the investigator to inspect standard operational records, compute engine runtime logs, or Admin Activity audit logs (such as metadata changes and resource creation events), which are readable with standard viewer rights.
Google Cloud intentionally separates the permissions for viewing Admin Activity logs from Data Access logs. Because Data Access logs can contain personally identifiable information (PII) or sensitive operational access records, Google Cloud restricts them to principals holding private log viewing permissions.
The Logs Configuration Writer (roles/logging.configWriter) role is designed for administrators and automated pipelines that need to manage log routing rules, destinations, and storage boundaries within Cloud Logging.
logging.privateLogEntries.list permission required to read Data Access audit logs. The investigator would be unable to inspect the actual log entries.The user needed to configure an aggregated log sink to export audit logs to a centralized BigQuery dataset or Cloud Storage bucket for long-term retention without needing full administrator privileges.
Confusing configuration roles with viewing roles is a common IAM misconception. A "Writer" role in logging configuration refers to writing architectural settings (like sinks and buckets), not reading or analyzing the log entries themselves.
The Logging Admin (roles/logging.admin) role provides full administrative control over all features, settings, and resources within Cloud Logging for a given project, folder, or organization.
logging.sinks.*, logging.buckets.*, and logging.exclusions.*.The user were a senior cloud operations administrator tasked with designing, configuring, maintaining, and managing the organization's entire Cloud Logging infrastructure, rather than a read-only compliance investigator.
While a Logging Admin can perform auditing functions, assigning administrative roles to personnel who only require inspection rights violates standard compliance frameworks and enterprise governance principles.
The Private Logs Viewer (roles/logging.privateLogViewer) is a specialized predefined Identity and Access Management (IAM) role in Google Cloud. It provides permissions to read and query private and sensitive log entries, specifically Data Access audit logs, across log buckets such as _Default and _Required.
roles/logging.privateLogViewer contains the logging.privateLogEntries.list permission, which is explicitly required to search, list, and read Data Access audit logs.gcloud logging).Standard viewer roles purposefully exclude Data Access audit logs because they frequently contain sensitive contextual information, including user emails and data access parameters. Granting Private Logs Viewer ensures the investigator has the exact read permissions necessary to inspect the incident without receiving unwanted write or administrative capabilities.
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