Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data team is operating an automated data processing pipeline deployed on Google Cloud. During a scheduled run, a task fails prematurely because custom transformation code encounters an unexpected schema variation and raises an unhandled exception.
Which type of log in Cloud Logging should the data engineer inspect to examine the stack trace and debugging messages generated by the code?
Data Access audit logs record API calls that read resource configurations, read resource metadata, or read/write user-provided resource data (such as reading an object from Cloud Storage or running a query in BigQuery).
storage.objects.get), but they do not capture internal program execution, function calls, or unhandled exceptions in custom data code.stdout or stderr are stored in application logs, not data access audit logs.The team needed to identify which user or service account read or modified specific data objects within a Cloud Storage bucket or BigQuery table.
While Data Access logs can verify whether a pipeline service account successfully connected to a storage bucket, they cannot explain why a data transformation script crashed after reading the data.
Application logs capture runtime events, diagnostics, status messages, and unhandled errors emitted directly by user code, container processes, or application software during execution. In Google Cloud services such as Cloud Run, Compute Engine, and Cloud Functions, standard output (stdout) and standard error (stderr) streams are automatically collected by Cloud Logging as application-level logs.
logger.error(), logger.info()) within data processing scripts, allowing engineers to trace the exact input data or schema anomaly that caused the job to abort.DEBUG, INFO, WARNING, ERROR, and CRITICAL.Application logs directly capture software behavior and code output. While platform audit logs or network logs show administrative API requests and network connections, only application logs contain the internal programmatic details and error stack traces necessary to fix data transformation failures.
Admin Activity audit logs record administrative actions that modify the configuration or metadata of Google Cloud resources. These logs record specific API calls such as creating, updating, or deleting compute instances, storage buckets, or IAM policies.
The scenario required determining which user or service account modified a pipeline's infrastructure settings, deleted a compute resource, or updated an IAM access policy.
Audit logs are essential for compliance, security auditing, and change tracking, but they do not serve as runtime diagnostic tools for debugging application source code.
Firewall Rule logs (or Network Access logs) capture TCP and UDP connection attempts that are either allowed or denied by VPC firewall rules. They record connection metadata including source/destination IP addresses, ports, and protocols.
The data pipeline failed with a network timeout error because a newly deployed firewall rule was blocking outbound traffic to an external database.
Network and access logs are crucial for verifying network reachability and perimeter security, but application logs remain the primary tool for diagnosing code execution exceptions.
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