Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise runs a Dataflow streaming pipeline that ingests audit logs from Pub/Sub, applies in-flight transformations using a JavaScript User-Defined Function (UDF), and exports the events to an external monitoring endpoint (Splunk HEC).
During a system alert triggered by high backlog on the unprocessed dead-letter subscription, a data engineer analyzes Cloud Logging and error attributes attached to failed records:
Splunk write status code: 503 and Read timed out.errorMessage attributes showing Splunk write status code: 403 and ReferenceError: device_id is not defined.How should the data engineer classify these errors and remediate the pipeline to ensure full data recovery?
In enterprise event streaming architectures using Cloud Dataflow and Pub/Sub, errors are categorized into transient errors (temporary server overload or network blips) and persistent/systemic errors (authentication failures or syntax/runtime bugs in transformation code). Transient errors can be resolved with automated retries, while persistent errors require manual code or configuration intervention followed by dead-letter replay.
503 Service Unavailable and network socket Read timed out errors occur due to temporary endpoint throttling or network latency spikes. The pipeline natively applies exponential backoff to re-deliver these without routing them to the dead-letter queue.403 Forbidden indicates an invalid or expired authentication token (HEC token), and ReferenceError: device_id is not defined indicates a breaking syntax or variable scope defect inside the JavaScript User-Defined Function (UDF). Because retrying identical payloads against these errors will never succeed, the pipeline forwards them to the unprocessed topic to prevent blocking pipeline execution.5xx errors are already handled automatically by the underlying runner.This solution correctly diagnoses both error types using structured log properties, avoids unnecessary intervention for self-healing transient errors, and implements the standard dead-letter replay operational pattern recommended for Google Cloud stream processing.
This option assumes the errors are entirely systemic IAM permission issues affecting the Dataflow worker service account inside Google Cloud, and suggests applying broad administrative roles and draining the pipeline.
403 error is generated by the external destination API (Splunk HTTP Event Collector), not Google Cloud IAM. Granting Google Cloud administrative IAM roles (roles/pubsub.admin or roles/dataflow.admin) has no bearing on third-party endpoint authentication.admin roles to worker service accounts introduces substantial security risks and violates GCP best practices.The worker logs contained Google Cloud API access errors, such as PERMISSION_DENIED when accessing Cloud Storage staging buckets or Pub/Sub subscription pull endpoints.
This option treats all observed HTTP status codes (503 and 403) and JavaScript runtime errors as temporary downstream backpressure symptoms, proposing horizontal scaling of worker VMs and increasing retry thresholds.
ReferenceError: device_id is not defined is a deterministic code defect in the User-Defined Function (UDF). Adding compute capacity or increasing retry counts cannot resolve a missing variable declaration or malformed code.403 Forbidden indicates an authorization failure (such as an invalid API token), not compute or memory exhaustion. Scaling worker VMs does not fix security permissions.The errors were solely limited to worker CPU saturation or generic network queue delays without any 4xx client status codes or transformation code exceptions.
This option diagnoses the issue as Java Virtual Machine garbage collection thrashing, recommends enabling Streaming Engine, suppressing application log levels, and discarding unprocessed dead-letter records.
OutOfMemoryError or gc thrashing=true log indicators.The pipeline logs displayed explicit JVM heap exhaustion errors, high pushback rates, and out-of-memory indicators rather than HTTP error codes and JavaScript runtime failures.
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