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.
An administrator is monitoring an active Cloud Dataflow streaming pipeline that uses Streaming Engine. During a sudden surge in incoming traffic, message latency increases and an unprocessed backlog accumulates, but Dataflow stops provisioning additional worker instances.
Which chart in the Dataflow monitoring interface should the administrator inspect to determine the specific reason the autoscaler did not provision more workers?
The Worker CPU utilization chart displays the average and peak CPU consumption across all active Compute Engine worker instances in a Dataflow pipeline over time. It allows operators to see whether worker instances are CPU-bound or underutilized.
While high CPU utilization serves as an input signal to trigger autoscaling, the chart itself only displays hardware performance data. It cannot explain the internal logic of the autoscaler or clarify why scaling halted when limits are reached.
The objective was to verify whether the pipeline's computational logic is consuming high processor capacity or if workers are sitting idle due to I/O bottlenecks.
The Execution graph visualizes the directed acyclic graph (DAG) of transforms within a Dataflow pipeline, showing metrics such as input/output throughput rates, processing times, and system lag for individual transforms.
Inspecting individual graph steps helps identify specific transforms that are slow, but it does not detail worker provisioning logic or explain why the cluster autoscaler stopped adding Compute Engine VMs.
The administrator needed to pinpoint which individual transform step was creating a bottleneck within the pipeline code.
The Autoscaling rationale chart in Cloud Dataflow provides insight into the automated decision-making process of the Dataflow autoscaler for Streaming Engine jobs. It visualizes whether the autoscaler chose to scale up, scale down, or keep the worker pool size unchanged during specific time windows.
When a pipeline experiences an increasing backlog and rising latency, Dataflow typically scales out worker instances to handle the throughput. If worker growth halts despite a growing backlog, the Autoscaling rationale chart displays the explicit reason behind the decision. By hovering over data points in the chart, administrators can view descriptions such as:

--maxNumWorkers.While raw operational metrics show symptoms like high utilization or backlogs, the Autoscaling rationale chart is the only monitoring tool that directly explains the operational decisions of the autoscaler engine.
The Backlog metric chart (available for Streaming Engine pipelines) tracks the estimated volume of unprocessed data remaining in the input queue over time, measured in seconds of throughput or byte volume.
The backlog chart illustrates that a queue is accumulating, confirming that the pipeline is falling behind. However, it does not provide the underlying rationale for why the autoscaler declined to add more workers.
The administrator needed to measure the total amount of unread data waiting in an upstream messaging system to evaluate SLA compliance.
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