Data access logs in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Data Access Logs Activation

You enable Data Access logs for a Google Cloud Storage bucket. What is the expected behavior immediately after enabling these logs?

A Data Access logs only record write operations, not read operations.

B Data Access logs start recording all read and write operations on the bucket immediately.

C Data Access logs start recording only after 24 hours delay from enabling.

D Data Access logs are not generated unless Audit Logs API is explicitly called.

💡 Hint

Think about what Data Access logs are designed to capture in Google Cloud.

Data Access logs capture both read and write operations immediately after enabling, providing detailed audit information.

❓ security

intermediate

Permissions Required for Viewing Data Access Logs

Which IAM role is required for a user to view Data Access logs in Google Cloud's Cloud Logging?

A roles/audit.logReader

B roles/storage.objectViewer

C roles/logging.viewer

D roles/owner

💡 Hint

Consider which role grants read access to logs in Cloud Logging.

The roles/logging.viewer role allows users to read logs, including Data Access logs, in Cloud Logging.

❓ Architecture

advanced

Designing a Secure Audit Logging Architecture

You want to ensure Data Access logs for BigQuery are immutable and stored securely for compliance. Which architecture best achieves this?

A Export Data Access logs to a Cloud Storage bucket with Object Versioning and Bucket Lock enabled.

B Store Data Access logs only in Cloud Logging with default retention settings.

C Export Data Access logs to BigQuery and allow users to modify the logs as needed.

D Send Data Access logs to Pub/Sub and delete them after 30 days.

💡 Hint

Think about how to make logs tamper-proof and retained for compliance.

Exporting logs to Cloud Storage with Object Versioning and Bucket Lock ensures logs are immutable and retained securely.

❓ Configuration

advanced

Configuring Data Access Logs for Cloud SQL

Which configuration step is necessary to enable Data Access logs for Cloud SQL instances?

A Enable Data Access logs in Cloud Audit Logs settings and configure export to Cloud Logging.

B Enable SQL Insights and Data Access logs are automatically enabled.

C Set the Cloud SQL instance to private IP mode to activate Data Access logs.

D Create a custom IAM role with Cloud SQL Admin permissions to enable logs.

💡 Hint

Consider where Data Access logs are managed in Google Cloud.

Data Access logs are enabled via Cloud Audit Logs settings and can be exported to Cloud Logging for Cloud SQL.

✅ Best Practice

expert

Optimizing Cost and Retention for Data Access Logs

Your organization generates large volumes of Data Access logs daily. What is the best practice to optimize cost while retaining logs for 1 year?

A Disable Data Access logs and rely on System Event logs for auditing.

B Keep all Data Access logs only in Cloud Logging with default retention of 30 days.

C Export logs to BigQuery without partitioning and keep indefinitely.

D Export Data Access logs to Cloud Storage with Nearline storage class and set lifecycle to delete after 1 year.

💡 Hint

Think about storage classes and lifecycle policies for cost-effective long-term retention.

Using Cloud Storage Nearline with lifecycle policies balances cost and retention for large volumes of logs.

Practice

1. What is the main purpose of data access logs in Google Cloud?

easy

A. To reduce storage costs

B. To record who accessed or changed your cloud data

C. To automatically backup your data

D. To increase the speed of data processing

Solution

1. Step 1: Understand what data access logs record

   Data access logs track user actions on cloud data, such as access or changes.

2. Step 2: Identify the main purpose

   The main goal is to monitor and audit who accessed or modified data for security and compliance.

3. Final Answer:

   To record who accessed or changed your cloud data -> Option B

4. Quick Check:

   Data access logs = record access and changes [OK]

Hint: Logs track data access and changes, not performance or cost [OK]

Common Mistakes:

• Confusing logs with backup or performance tools
• Thinking logs reduce costs automatically
• Assuming logs speed up data processing

2. Which of the following is the correct way to enable data access logs for a Google Cloud service?

easy

A. Install a logging agent on your local machine

B. Create a firewall rule to allow logging

C. Use Cloud Storage lifecycle rules

D. Enable audit logs in Cloud IAM & Admin for the service

Solution

1. Step 1: Identify how to enable data access logs

   Data access logs are enabled by configuring audit logs in Cloud IAM & Admin for the specific service.

2. Step 2: Eliminate unrelated options

   Firewall rules, local agents, and storage lifecycle rules do not enable audit logging.

3. Final Answer:

   Enable audit logs in Cloud IAM & Admin for the service -> Option D

4. Quick Check:

   Audit logs enabled via IAM & Admin [OK]

Hint: Audit logs are enabled in IAM & Admin, not by firewall or agents [OK]

Common Mistakes:

• Confusing firewall rules with logging setup
• Thinking local agents enable cloud audit logs
• Using storage lifecycle rules for logging

3. Given this filter for a logging sink:
resource.type="bigquery_resource" AND protoPayload.methodName="tableservice.insert"
What logs will this sink collect?

medium

A. All Cloud Storage bucket creations

B. All BigQuery query executions

C. All BigQuery table creation events

D. All Compute Engine VM starts

Solution

1. Step 1: Analyze the filter components

   The filter targets resource type 'bigquery_resource' and method 'tableservice.insert', which means table creation in BigQuery.

2. Step 2: Match filter to log events

   This filter collects logs about BigQuery tables being created, not queries or other services.

3. Final Answer:

   All BigQuery table creation events -> Option C

4. Quick Check:

   Filter matches BigQuery table inserts [OK]

Hint: Look for resource type and method name to identify event type [OK]

Common Mistakes:

• Confusing table creation with query execution
• Mixing BigQuery with Cloud Storage or Compute Engine
• Ignoring methodName in filter

4. You created a logging sink to export data access logs to BigQuery but see no data arriving. What is a likely cause?

medium

A. Data access logs are disabled in the project

B. BigQuery dataset is in a different region

C. The sink uses a Cloud Storage bucket instead of BigQuery

D. The sink filter excludes data access logs

Solution

1. Step 1: Check if data access logs are enabled

   If data access logs are disabled, no logs will be generated or exported.

2. Step 2: Consider other causes

   While filters and regions matter, the most common cause is logs not enabled at all.

3. Final Answer:

   Data access logs are disabled in the project -> Option A

4. Quick Check:

   Logs must be enabled to export data [OK]

Hint: Verify logs are enabled before checking sinks [OK]

Common Mistakes:

• Assuming filter or region is always the problem
• Confusing sink destination with log generation
• Not enabling data access logs in IAM & Admin

5. You want to audit all data access to Cloud Storage buckets in your project and store logs in BigQuery for analysis. Which steps should you take?

hard

A. Enable data access audit logs for Cloud Storage, create a sink with filter resource.type="gcs_bucket", export to BigQuery dataset

B. Enable system logs only, create a sink exporting all logs to Cloud Storage

C. Install logging agents on VMs, export logs to BigQuery without filters

D. Create a firewall rule to allow logging traffic, enable data access logs

Solution

1. Step 1: Enable data access audit logs for Cloud Storage

   This ensures logs capture who accessed or changed Cloud Storage buckets.

2. Step 2: Create a sink with filter resource.type="gcs_bucket" and export to BigQuery

   This filters logs to only Cloud Storage bucket access and stores them in BigQuery for analysis.

3. Final Answer:

   Enable data access audit logs for Cloud Storage, create a sink with filter resource.type="gcs_bucket", export to BigQuery dataset -> Option A

4. Quick Check:

   Enable logs + filter + export to BigQuery = audit setup [OK]

Hint: Enable logs, filter by resource, export to BigQuery [OK]

Common Mistakes:

• Using system logs instead of data access logs
• Exporting all logs without filtering
• Relying on firewall rules for logging