Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing a compliance and auditing architecture across its Google Cloud organization while optimizing Cloud Logging storage and ingestion costs. The security operations team has established the following requirements:
_Default log bucket.Which combination of audit log configurations and IAM roles should you implement?
roles/logging.privateLogViewer) role.Cloud Audit Logs provide visibility into actions executed across Google Cloud environments by answering "Who did what, where, and when?". Admin Activity logs capture configuration and metadata writes (ADMIN_WRITE), while System Event logs record automated actions taken by Google Cloud systems that alter resource states. Data Access audit logs capture metadata reads (ADMIN_READ), data reads (DATA_READ), and data writes (DATA_WRITE). The Private Logs Viewer (roles/logging.privateLogViewer) role provides permission to read all log types including sensitive Data Access logs in the _Default log bucket.
DATA_READ and DATA_WRITE) only for services hosting sensitive data fulfills the auditing requirement while controlling storage spend.roles/logging.privateLogViewer grants auditors access to view Admin Activity, System Event, Policy Denied, and Data Access audit logs located in the _Default bucket.This architecture accurately leverages default log generation for control plane events, targets high-volume Data Access logging selectively to optimize costs, and uses the correct IAM role needed to inspect private data logs in the default storage bucket.
roles/logging.viewer) role.This option attempts to manually enable Admin Activity and System Event logs while disabling Data Access audit logs and granting the standard Logs Viewer (roles/logging.viewer) role.
DATA_READ and DATA_WRITE operations, failing the requirement to monitor interactions with sensitive user data.roles/logging.viewer role does not have permission to view Data Access audit logs in the _Default bucket.DATA_READ/DATA_WRITE).The organization only needed to monitor control plane and system configuration changes while completely excluding user data interaction tracking and restricting auditors to standard log viewing.
roles/logging.privateLogViewer) role.This option assumes Data Access audit logs are written by default and attempts to explicitly enable Policy Denied logs while assigning the Private Logs Viewer (roles/logging.privateLogViewer) role.
DATA_READ and DATA_WRITE operations because Data Access logs must be explicitly enabled.Data Access logs were enabled by default across all Google Cloud services and Policy Denied logging required explicit activation in the IAM audit configuration.
roles/logging.viewer) role.This approach enables Data Access audit logs globally across the organization, creates exclusion filters on Admin Activity logs to reduce ingestion volume, and assigns the standard Logs Viewer (roles/logging.viewer) role to compliance auditors.
roles/logging.viewer cannot view Data Access audit logs stored in the _Default bucket, preventing them from auditing data access events.Admin Activity logs incurred high storage costs and the auditors only required access to non-private system logs.
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