Which Google Cloud Service Unifies Batch and Stream Processing
Designing network, storage, and compute resources.
Designing a solution infrastructure that meets technical requirements.
Your company has successfully migrated to the cloud and wants to analyze their data stream to optimize operations. They do not have any existing code for this analysis, so they are exploring all their options. These options include a mix of batch and stream processing, as they are running some hourly jobs and live- processing some data as it comes in. Which technology should they use for this?
Answer
Correct answer: B — Use Google Cloud Dataflow, the serverless unified batch and stream processing service, for hourly jobs and live stream analysis without managing infrastructure.
Community Insight
The question tests whether you can match a unified batch-plus-stream workload with no existing pipeline code to a managed service — the trap is picking a tool that handles only one mode or fixating on the word 'analyze' to choose BigQuery.
For a company with no existing code that must run both hourly batch jobs and live stream processing, Google Cloud Dataflow is the intended choice because it is a fully managed, serverless service built on Apache Beam that unifies batch and streaming in one programming model. The page explains why Dataflow beats Dataproc, Container Engine with Bigtable, and Compute Engine with BigQuery in this Professional Cloud Architect scenario.
The most common wrong answer is D (Compute Engine with BigQuery), because the word 'analyze' pulls learners toward the analytics warehouse; but BigQuery with VMs is not a unified processing framework, and learners defending this choice note the confusion themselves. A secondary mistake is A (Dataproc), since Spark can do streaming but Dataproc is a managed Hadoop/Spark cluster rather than a code-free unified pipeline service.
Community Discussion (55 comments)
Balakr6
👍 1
Selected: B
Fully Serverless, Choose if starting fresh or requiring streaming Analytics
Ral17
👍 1
Selected: B
Dataflow is built on Apache Beam, which was specifically designed for unified batch + stream processing. Google managed underlying infra and autoscales based on volume.
RamDhangar
👍 1
Selected: B
answer:B
hpf97
👍 2
Selected: B
DataFlow is a managed service which processes stream and batch data. So it prefectly fits the need
Ekramy_Elnaggar
👍 6
Selected: B
1. Unified Batch and Stream Processing: Dataflow is a fully managed service designed for both batch and stream data processing. This makes it ideal for your company's needs, as they require both hourly batch jobs and live stream processing. 2. No Existing Code: Dataflow provides a unified programming model and SDKs (Java, Python) for building data pipelines, which is beneficial since your company doesn't have existing code and needs to develop new solutions. 3. Serverless and Scalable: Dataflow is serverless, meaning you don't need to manage infrastructure. It automatically scales resources based on the workload, ensuring efficient processing of both batch and stream data. 4. Cost-Effective: Dataflow's autoscaling and pay-per-use model optimize costs by only utilizing resources when needed.
Singapore123
👍 4
Selected: B
B. Google Cloud Dataflow Explanation: Unified Processing: Google Cloud Dataflow is designed to handle both batch and stream processing in a unified manner. This means you can process data as it arrives (stream processing) and also perform scheduled batch jobs efficiently. Serverless and Scalable: Dataflow is serverless, which means you don’t have to worry about managing the underlying infrastructure. It automatically scales to handle varying workloads, making it ideal for optimizing operations based on live data streams and scheduled jobs. Integration with Other Google Cloud Services: Dataflow integrates well with other Google Cloud services, such as Google Cloud Storage, BigQuery, and Pub/Sub. This makes it easier to build a comprehensive data pipeline that can analyze data streams effectively. Flexible SDKs: Dataflow supports popular programming languages like Java and Python, allowing your team to write custom processing logic as needed.
Eroc
👍 40
All four options can accomplish what the question asks, in regards to batching and streaming processes. "A" is for Apache Spark and Hadoop, a juggernaut in speed of data processing. "B" is Google's best attempt at TIBCO, Ab Initio, and other processing technology, built explicity for visualizing batch operations and streams without through various labeled circuit boards. "C" and "D" are used within "A" and "B" and would require more work and higher risk. I'd guess Google wants you to select "B"
Hungdv
👍 1
Choose B
hzaoui
👍 1
Selected: B
B is correct
devakram
👍 2
chatGPT answers: B. Google Cloud Dataflow Google Cloud Dataflow is a fully managed service for stream and batch data processing. It is built on Apache Beam and provides a unified programming model, making it an ideal choice for scenarios where both batch and stream data processing are required. Dataflow simplifies the complexities of data parallel processing, allowing for easy development and maintenance of data processing pipelines. It integrates well with other Google Cloud services, like BigQuery for analytics and Cloud Storage for storing data, providing a comprehensive solution for real-time and batch data processing needs.
BiddlyBdoyng
👍 5
The word analysis throws me off. Wonder if the question is just written incorrectly here? I'd say Dataflow is a key tool to enable the processing of the data to be able to do the analysis but feels like the final analysis should be in a database.
alekonko
👍 2
Selected: B
B is the answer
Deb2293
👍 2
Selected: B
A is a managed Hadoop and Spark service. C and D are mostly for petabyte kinds of data. So remains B (suitable for ETL jobs)
omermahgoub
👍 3
To analyze a data stream and optimize operations, your company could consider using Google Cloud Dataflow, which is a fully-managed, cloud-native data processing service that can handle both batch and stream processing. Google Cloud Dataflow is designed to handle large volumes of data and can scale up or down automatically to meet the needs of the workload. It provides a number of pre-built connectors and integrations that make it easy to ingest data from a variety of sources, and it offers a range of processing options, including batch processing and stream processing, that can be used to analyze the data in real-time. Option A: Google Cloud Dataproc, option C: Google Container Engine with Bigtable, and option D: Google Compute Engine with Google BigQuery, while potentially useful for certain types of data processing, would not necessarily be well-suited to handle both batch and stream processing in the way that Google Cloud Dataflow can
thamaster
👍 2
answer is D for me the question is which tool for analyse data. Dataflow does not analyse data
megumin
👍 1
Selected: B
ok for B
Mahmoud_E
👍 1
Selected: B
B is the right answer
AzureDP900
👍 1
B is correct
minmin2020
👍 1
Selected: B
B. Google Cloud Dataflow
holerina
👍 1
correct is B use data flow for stream and batch process
Jay_Krish
👍 2
Selected: B
Answer seems to be B in most other websites as well. https://cloud.google.com/solutions/authenticating-corporate-users-in-a-hybrid-environment
Nirca
👍 1
Selected: B
Data flow is Air flow open source project. Is an ETL tool. Exactly for copying source data to destination; online or batch.
AWS56
👍 3
Selected: B
Google wants you to select "B" ---- +10000
anjuagrawal
👍 3
The questions is asking the solution for analysing and not for processing. DataFlow is to process batch and stream data but analysing for batch and stream is done with BigQuery. I would go with D
vincy2202
👍 3
B is the correct answer
cloud_enthusiast_in
👍 1
Reading the key words it is undoubted choice to mark Ans as B. But here they ased about 'analyze' and not 'process'. From that point D is answer but not sure how a compute engine will work. Also, may be the question setter has not differentiated between analyze and compute. I would say, an improper and not a serious question
haroldbenites
👍 2
Go for B
joe2211
👍 1
Selected: B
Dataflow for Batch and Streaming Data Processing
amxexam
👍 3
I will go against the flow.... The question clearly states they want to analyze their data stream to optimize operations that don't have any code. Let's go with option elimination A. Google Cloud Dataproc >> Data proc is a service to run big data analytics like sparks or presto, but is not ready to use like big query. B. Google Cloud Dataflow >> With data flow you will be able to process streams of data. The requirement is to analyze not process. C. Google Container Engine with Bigtable >> Provides storage and process but clients will have to put their own solution. D. Google Compute Engine with Google BigQuery >> BigQuery will provide analytics options. Not sure what compute engine will help.
Papafel
👍 1
B will be the correct answer: Dataflow is for processing both the Batch and Stream. Cloud Dataflow is a fully-managed service for transforming and enriching data in stream (real time) and batch (historical) modes with equal reliability and expressiveness -- no more complex workarounds or compromises needed. References: https://cloud.google.com/dataflow/
aviratna
👍 2
B. Dataflow is right option as user doesnt have their own code. Other options are applicable if user has own code which they wants to use for analysis.
victory108
👍 1
B. Google Cloud Dataflow
un
👍 1
B is correct answer
un
👍 1
B is correct
ronVenom
👍 1
Go with the FLOW - DataFlow
JohnWick2020
👍 3
My Answer - B. Keynotes from question: 1 - Want to analyze data stream to optimize operations. 2 - No existing code for analysis and want to explore (greenfield). 3 - Options - mix of batch and stream processing, hourly jobs, live processing. Explanation: A - Ok but DataProc is more hands-on/ devops-focused. Some config overhead setting up Apache/Haddop clusters. B - Correct; DataFlow is more hand-off / serverless and supports a variety of processing patterns. Dev worry less of infra setups and can focus more on their day jobs. C&D - incorrect; can rule out quickly these. Not viable options for batch or stream processing.
Ausias18
👍 1
Answer is B
Joyjit_Deb
👍 1
"B" - Dataflow seems to be the correct approach.
bnlcnd
👍 1
B: https://stackoverflow.com/questions/46436794/what-is-the-difference-between-google-cloud-dataflow-and-google-cloud-dataproc - Cloud Dataproc provides you with a Hadoop cluster, on GCP, and access to Hadoop-ecosystem tools (e.g. Apache Pig, Hive, and Spark); this has strong appeal if you are already familiar with Hadoop tools and have Hadoop jobs - Cloud Dataflow provides you with a place to run Apache Beam based jobs, on GCP, and you do not need to address common aspects of running jobs on a cluster (e.g. Balancing work, or Scaling the number of workers for a job; by default, this is automatically managed for you, and applies to both batch and streaming) -- this can be very time consuming on other systems
gianberg
👍 2
Everyone says B. Ok. But what about the requirement "wants to analyze their data"? Dataflow is an ETL for batch and streaming processing, but how to analyse your data? and where do you store data taht you want to analyze? So I choose A, the simplest service to work on batch and streaming processing and for data analysis.
Kiranazure
👍 1
B is correct
AshokC
👍 1
B - Dataflow can process both Batch and Streaming data
Musk
👍 2
DataFlow takes you the data to the engine that will analyze it, but is not a tool to analyze by itself. I'd go with D.
anjuagrawal
👍 2
Agree. I also go with D.
cookiethecat
👍 2
My answer : B
mlantonis
👍 3
batch and stream processing so you pick Dataflow. B is the correct.
Pupina
👍 2
B for sure
gfhbox0083
👍 2
B, for sure. Google Cloud Dataflow
Nirms
👍 2
B is the correct answer
Ziegler
👍 2
B is correct
AD2AD4
👍 2
Final Decision to go with Option B
clouddude
👍 3
I'll go with B. A does not seem reasonable as Dataproc is for Hadoop workloads. B seems reasonable because Dataflow can handle the ingestion of both batch and stream flows. C does not seem reasonable because it doesn't address the streaming requirement. D does not seem reasonable because it doesn't address the streaming requirement.
PRC
👍 2
Dataflow is the right choice for batch and real time data processing. "B"
desertlotus1211
👍 4
Answer is B: https://cloud.google.com/dataflow Fast, unified stream and batch data processing Dataflow is a fully managed streaming analytics service that minimizes latency, processing time, and cost through autoscaling and batch processing. With its serverless approach to resource provisioning and management, you have access to virtually limitless capacity to solve your biggest data processing challenges, while paying only for what you use.
2g
👍 6
answer: B
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Google Cloud Dataflow is a fully managed, serverless stream and batch analytics service built on Apache Beam, which provides a single unified programming model for both modes — so hourly batch jobs and live-processing of incoming data can live in one pipeline rather than two separate stacks. Because the company has no existing code, Dataflow's managed service model removes cluster provisioning, autoscaling, and operational overhead entirely; you simply define pipelines with the SDKs (Java, Python) and let Google handle execution. Commenters converged on this reasoning, with Ekramy_Elnaggar citing "Unified Batch and Stream Processing" and Singapore123 pointing to "Serverless and Scalable" behavior. desertlotus1211 backed this up with the official tagline of "Fast, unified stream and batch data processing" from the Dataflow product page. This is exactly the architectural fit the scenario describes: one technology covering both processing patterns with no code or infrastructure to maintain.Why the Other Options Are Wrong
Option A, Cloud Dataproc, is a managed Apache Spark/Hadoop service: as Eroc noted, it is "a juggernaut in speed of data processing," but it runs clusters you must size and manage and it is not the unified, code-free experience the no-existing-code constraint implies. Option C pairs Container Engine (GKE) with Bigtable, a low-latency NoSQL store — Bigtable holds and serves high-throughput data but is not a batch/stream processing engine, so you would still have to build all processing yourself. Option D pairs Compute Engine with BigQuery: BigQuery is excellent for analytics queries and does support streaming inserts and scheduled batch queries, but the question asks for the technology that processes the mixed workload, and provisioning VMs alongside a warehouse is neither unified nor serverless. As anjuagrawal argued for D because "The questions is asking the solution for analysing and not for processing," the actual scenario describes running hourly jobs and live-processing data — a processing requirement that Dataflow satisfies before any downstream analysis happens.Community Comment Notes
Most commenters selected B and several explained why, with AWS56 quipping "Google wants you to select \"B\" ---- +10000" and vincy2202 simply stating "B is the correct answer." Eroc made a fair nuance that "All four options can accomplish what the question asks, in regards to batching and streaming processes," but the tiebreaker is the no-existing-code, fully managed requirement. BiddlyBdoyng and anjuagrawal both flagged that "The word analysis throws me off" and suggested BigQuery for the final analytics layer — a legitimate architecture note, since analysis can follow processing, but it does not change which service should perform the unified batch and stream work described here.Official Reference
Exam Strategy
In PCA scenario questions, treat keywords like 'batch and stream' plus 'no existing code / managed' as signposts for a specific Google Cloud product — here they point straight to Dataflow. If two options both plausibly 'do the job,' pick the serverless, fully managed, unified option rather than one requiring you to provision clusters or VMs.
Frequently Asked Questions
Why not BigQuery when the question says the company wants to analyze their data stream?
BigQuery is the analytics destination, but the scenario describes processing requirements — hourly jobs plus live-processing data as it arrives. Dataflow performs that unified batch and stream processing, after which results can be loaded into BigQuery for analysis.
Can't Dataproc handle both batch and stream with Spark?
Spark on Dataproc can run both, but Dataproc requires you to provision and manage clusters. With no existing code, Dataflow's serverless Beam model is the simpler, officially preferred answer.
Related Analysis
Practice All PCA Questions
Access 81 questions with complete answers and detailed explanations.
View Full PCA Practice Test →