How to Configure an ML Feature Pipeline on GCP?
You work at a large organization that recently decided to move their ML and data workloads to Google Cloud. The data engineering team has exported the structured data to a Cloud Storage bucket in Avro format. You need to propose a workflow that performs analytics, creates features, and hosts the features that your ML models use for online prediction. How should you configure the pipeline?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests the ability to select the appropriate Google Cloud services for specific data processing tasks, distinguishing between analytical databases (BigQuery) and transactional databases (Spanner), and identifying the correct solution for low-latency online serving.
The optimal workflow involves using BigQuery for analytics, Dataflow for feature engineering, and Vertex AI Feature Store for low-latency online serving. The community consensus confirms that this combination effectively addresses the requirements for analysis, transformation, and hosting.
A common error is selecting Cloud Spanner for analytics, as it is an OLTP database designed for transactional consistency rather than large-scale analytical processing.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
BigQuery is the correct choice for performing analytics on structured data like Avro files because it is a serverless, highly scalable enterprise data warehouse. Dataflow is the ideal service for creating features, as it provides a serverless execution environment for robust data processing pipelines using Apache Beam. Finally, Vertex AI Feature Store is specifically designed to host and serve features for online prediction with low latency, which standard databases cannot efficiently provide.Why the Other Options Are Wrong
Options A and C incorrectly suggest using Cloud Spanner for analytics; Spanner is optimized for horizontal scaling and strong consistency in transactional workloads, not for running analytical queries. Option D incorrectly proposes storing features in BigQuery for online prediction; while BigQuery is excellent for batch analytics and training, it is not designed for the low-latency, high-throughput serving required for real-time online predictions.Community Comment Notes
Community members strongly support Option B, emphasizing that BigQuery is designed for large-scale analytics while Spanner is suited for transactional workloads. Commenters also highlighted that Vertex AI Feature Store is the dedicated service for managing and serving features for online prediction, ensuring the necessary performance for ML models.Official Reference
Exam Strategy
When designing ML workflows, map the specific technical requirement to the service's core strength: BigQuery for analytics, Dataflow for complex ETL/feature engineering, and Vertex AI Feature Store for low-latency serving. Avoid using transactional databases like Spanner for analytical reporting.
Related Analysis
Practice All PMLE Questions
Access 65 questions with complete answers and detailed explanations.
View Full PMLE Practice Test →