Google Professional Machine Learning Engineer Exam Dumps and Practice Test Questions Set 12 Q166-180

Visit here for our full Google Professional Machine Learning Engineer exam dumps and practice test questions.

Question 166

A bank wants to implement real-time loan approval scoring. The system must handle thousands of applications per second, provide low-latency decisions, and adapt to changing customer behavior and credit risk. Which architecture is most appropriate?

A) Batch process applications daily and manually evaluate credit risk
B) Use Pub/Sub for real-time application ingestion, Dataflow for feature computation, and Vertex AI Prediction for online scoring
C) Store customer data in spreadsheets and manually compute credit scores
D) Train a model once on historical applications and deploy it permanently

Answer: B

Explanation:

Batch processing applications daily and manually evaluating credit risk is insufficient for real-time loan approval. Credit decisions are often required instantly, and daily batch processing introduces delays, which is unacceptable for both customers and operational requirements. Manual evaluation cannot scale to handle thousands of applications efficiently and is prone to human error. Batch workflows also do not allow continuous retraining, preventing adaptation to evolving customer behavior and credit risk patterns. This approach is unsuitable for modern banking operations where immediate and accurate scoring is critical.

Using Pub/Sub for real-time application ingestion, Dataflow for feature computation, and Vertex AI Prediction for online scoring is the most appropriate solution. Pub/Sub enables continuous ingestion of loan application data, ensuring that no applications are missed. Dataflow pipelines compute derived features such as debt-to-income ratios, historical payment patterns, credit utilization, and recent financial behaviors. Vertex AI Prediction provides low-latency scoring, allowing immediate decision-making for loan approvals. Continuous retraining pipelines ensure models adapt to changes in customer behavior, economic conditions, or updated regulatory policies, improving predictive accuracy over time. Autoscaling ensures that high application volumes are handled efficiently. Logging, monitoring, and reproducibility provide operational reliability, auditability, and compliance with banking regulations. This architecture supports scalable, low-latency, and continuously adaptive credit scoring.

Storing customer data in spreadsheets and manually computing credit scores is impractical. Spreadsheets cannot handle high-frequency, high-volume application data efficiently. Manual computation is slow, error-prone, and non-reproducible, making it unsuitable for operational loan scoring.

Training a model once on historical applications and deploying it permanently is inadequate. Customer financial behavior and credit risk evolve continuously, and a static model cannot adapt, leading to decreased accuracy and potential financial risk. Continuous retraining and online scoring are essential to maintain operational effectiveness and compliance.

The optimal solution is Pub/Sub for real-time ingestion, Dataflow for feature computation, and Vertex AI Prediction for online scoring, providing scalable, low-latency, and continuously adaptive loan approval scoring.

Question 167

A logistics company wants to optimize delivery routes dynamically using real-time vehicle telemetry, traffic data, and weather conditions. The system must scale to thousands of vehicles, provide low-latency route recommendations, and continuously adapt to changing conditions. Which solution is most appropriate?

A) Batch process delivery and traffic data daily, and manually update routes
B) Use Pub/Sub for real-time data ingestion, Dataflow for feature computation, and Vertex AI Prediction for online routing optimization
C) Store vehicle and traffic data in spreadsheets and manually compute optimal routes
D) Train a route optimization model once and deploy it permanently

Answer: B

Explanation:

Batch processing, delivery, and traffic data daily, and manually updating routes is insufficient for real-time route optimization. Traffic congestion, vehicle availability, and weather conditions change frequently, and daily updates result in outdated route recommendations. Manual computation cannot scale to thousands of vehicles and is prone to human error. Without continuous retraining and real-time feature computation, the system cannot adapt to changing patterns, reducing operational efficiency and customer satisfaction. This approach is unsuitable for enterprise logistics requiring dynamic and low-latency route optimization.

Using Pub/Sub for real-time data ingestion, Dataflow for feature computation, and Vertex AI Prediction for online routing optimization is the most appropriate solution. Pub/Sub ingests telemetry, traffic, and weather data continuously, ensuring that all updates are captured. Dataflow pipelines compute derived features such as expected delays, congestion impact, and vehicle availability, which are critical inputs for route optimization. Vertex AI Prediction delivers low-latency routing recommendations to dispatch systems, enabling immediate adjustments to routes. Continuous retraining pipelines allow models to adapt to evolving traffic patterns, vehicle behavior, and environmental changes, ensuring forecasts remain accurate and actionable. Autoscaling ensures efficient processing during peak delivery periods. Logging, monitoring, and reproducibility provide operational reliability, traceability, and governance compliance. This architecture enables scalable, low-latency, and continuously adaptive route optimization.

Storing vehicle and traffic data in spreadsheets and manually computing optimal routes is impractical. Spreadsheets cannot efficiently process high-volume telemetry and traffic data. Manual computation is slow, error-prone, non-reproducible, and cannot support continuous retraining or adaptation.

Training a route optimization model once and deploying it permanently is inadequate. Traffic, vehicle availability, and weather conditions change continuously, and a static model cannot adapt. Continuous retraining and online computation are essential for maintaining operational efficiency and accurate routing recommendations.

The optimal solution is Pub/Sub for real-time ingestion, Dataflow for feature computation, and Vertex AI Prediction for online routing optimization, providing scalable, low-latency, and continuously adaptive routing.

Question 168

A retailer wants to forecast product demand across multiple stores using historical sales, promotions, holidays, and weather conditions. The system must scale to millions of records, allow feature reuse, and continuously update forecasts. Which solution is most appropriate?

A) Train separate models locally for each store using spreadsheets
B) Use Vertex AI Feature Store for centralized features and Vertex AI Training for distributed forecasting
C) Store historical sales data in Cloud SQL and train a single global linear regression model
D) Use a simple rule-based system based on last year’s sales

Answer: B

Explanation:

Training separate models locally for each store using spreadsheets is impractical. Retail datasets include millions of records across hundreds of stores and multiple products, covering features such as historical sales, promotions, holidays, and weather. Local training cannot efficiently process this volume and is slow, error-prone, and non-reproducible. Managing features separately for each store introduces redundancy and inconsistency. Automated retraining pipelines are difficult to implement locally, and feature reuse is limited. This approach is unsuitable for enterprise-level demand forecasting that requires accuracy, scalability, and automation.

Using Vertex AI Feature Store for centralized features and Vertex AI Training for distributed forecasting is the most appropriate solution. Feature Store ensures consistent, reusable features across multiple models, reducing duplication and ensuring training and serving consistency. Vertex AI Training supports distributed training across GPUs or TPUs, efficiently processing millions of historical records while capturing complex patterns in sales, promotions, holidays, and weather. Automated pipelines handle feature updates, retraining, and model versioning, ensuring forecasts continuously improve as new data becomes available. Autoscaling allows efficient handling of large datasets. Logging, monitoring, and experiment tracking provide reproducibility, operational reliability, and governance compliance. This architecture enables scalable, accurate, and continuously updated inventory demand forecasts across multiple stores and products.

Storing historical sales data in Cloud SQL and training a single global linear regression model is insufficient. Cloud SQL is not optimized for large-scale analytical workloads, and linear regression cannot capture complex nonlinear relationships. A single global model may underfit, producing inaccurate forecasts and lacking localized precision.

Using a simple rule-based system based on last year’s sales is inadequate. Rule-based approaches cannot account for promotions, holidays, weather, or changing trends. They lack scalability, automation, and predictive accuracy, making them unsuitable for enterprise-level demand forecasting.

The optimal solution is Vertex AI Feature Store combined with Vertex AI Training, providing scalable, reusable, and continuously updated inventory demand forecasts.

Question 169

A healthcare provider wants to predict patient readmission risk using EHR data, lab results, and imaging. The system must scale with growing datasets, comply with privacy regulations, and allow reproducible training pipelines. Which approach is most appropriate?

A) Download all patient data locally and train models manually
B) Use BigQuery for structured data, Cloud Storage for unstructured data, and Vertex AI Pipelines for preprocessing, training, and deployment
C) Store patient data in spreadsheets and manually compute readmission risk
D) Train a model once using sample data and deploy it permanently

Answer: B

Explanation:

Downloading all patient data locally and training models manually is impractical due to privacy, compliance, and scalability concerns. EHR data is highly sensitive and regulated under HIPAA and other healthcare regulations. Local storage increases the risk of unauthorized access, and manual workflows are slow, error-prone, and non-reproducible. Local training cannot efficiently process heterogeneous datasets, including structured lab results and unstructured imaging. Manual preprocessing introduces inconsistencies and prevents automated retraining, which is necessary to maintain model accuracy over time. This approach fails to meet operational and regulatory requirements for healthcare predictive analytics.

Using BigQuery for structured data, Cloud Storage for unstructured data, and Vertex AI Pipelines for preprocessing, training, and deployment is the most appropriate solution. BigQuery handles structured EHR data efficiently, enabling scalable querying and aggregation of patient demographics, lab results, medication history, and vitals. Cloud Storage securely stores unstructured data, such as clinical notes and imaging files, ensuring scalable access while maintaining privacy compliance. Vertex AI Pipelines orchestrates preprocessing, feature extraction, training, and deployment in a reproducible manner, ensuring consistency and traceability. Continuous retraining pipelines allow models to adapt to new patient data, emerging treatments, and evolving clinical guidelines, maintaining predictive accuracy. Logging, monitoring, and experiment tracking ensure operational reliability, auditability, and privacy compliance. Autoscaling allows the processing of growing datasets efficiently. This architecture provides secure, scalable, reproducible, and continuously adaptive readmission risk prediction.

Storing patient data in spreadsheets and manually computing readmission risk is inadequate. Spreadsheets cannot handle large-scale structured and unstructured healthcare data. Manual computation is slow, error-prone, non-reproducible, and unsuitable for operational prediction or continuous retraining.

Training a model once using sample data and deploying it permanently is insufficient. Patient populations, treatments, and clinical protocols evolve. Static models cannot adapt to new patterns, resulting in reduced predictive accuracy. Continuous retraining and automated pipelines are necessary for operational effectiveness.

The optimal solution is BigQuery for structured data, Cloud Storage for unstructured data, and Vertex AI Pipelines for secure, scalable, reproducible, and continuously adaptive readmission risk prediction.

Question 170

A retailer wants to forecast inventory demand across multiple stores using historical sales, promotions, holidays, and weather. The system must scale to millions of records, allow feature reuse, and continuously update forecasts. Which solution is most appropriate?

Answer: B

Explanation:

Training separate models locally for each store using spreadsheets is impractical. Retail datasets consist of millions of records across hundreds of stores and multiple products, covering features such as historical sales, promotions, holidays, and weather. Local training cannot handle this scale efficiently and is slow, error-prone, and non-reproducible. Managing features separately for each store introduces redundancy and inconsistency. Automated retraining pipelines are difficult to implement locally, and feature reuse is limited. This approach is unsuitable for enterprise-level demand forecasting that requires accuracy, scalability, and automation.

Using Vertex AI Feature Store for centralized features and Vertex AI Training for distributed forecasting is the most appropriate solution. Feature Store ensures consistent, reusable features across multiple models, reducing duplication and ensuring training-serving consistency. Vertex AI Training supports distributed training across GPUs or TPUs, efficiently processing millions of historical records while capturing complex patterns in sales, promotions, holidays, and weather. Automated pipelines handle feature updates, retraining, and model versioning, ensuring forecasts continuously improve as new data becomes available. Autoscaling allows efficient handling of large data volumes. Logging, monitoring, and experiment tracking provide reproducibility, operational reliability, and governance compliance. This architecture enables scalable, accurate, and continuously updated inventory demand forecasts across multiple stores and products.

Storing historical sales data in Cloud SQL and training a single global linear regression model is insufficient. Cloud SQL is not optimized for large-scale analytical workloads, and linear regression cannot capture non-linear relationships. A single global model may underfit and produce inaccurate forecasts, lacking localized store-level precision.

The optimal solution is Vertex AI Feature Store combined with Vertex AI Training, providing scalable, reusable, and continuously updated inventory demand forecasts.

Question 171

A telecommunications company wants to detect network anomalies in real time using device logs. The system must scale to millions of log entries per second, provide low-latency detection, and continuously adapt to new failure patterns. Which solution is most appropriate?

A) Batch process logs nightly and manually inspects for anomalies
B) Use Pub/Sub for log ingestion, Dataflow for feature computation, and Vertex AI Prediction for online anomaly detection
C) Store logs in spreadsheets and manually identify anomalies
D) Train a model once on historical logs and deploy it permanently

Answer: B

Explanation:

Batch processing logs nightly and manually inspecting for anomalies is insufficient for real-time network anomaly detection. Network conditions can change rapidly, and nightly batch processing introduces unacceptable delays, preventing timely detection. Manual inspection cannot scale to millions of log entries per second and is error-prone. Batch workflows also lack continuous retraining, which is essential for adapting to new failure patterns and evolving device behaviors. This approach is unsuitable for modern telecommunication operations requiring operational real-time monitoring and immediate response.

Using Pub/Sub for log ingestion, Dataflow for feature computation, and Vertex AI Prediction for online anomaly detection is the most appropriate solution. Pub/Sub enables high-throughput, real-time ingestion of device logs, ensuring that all events are captured. Dataflow pipelines continuously compute features such as latency spikes, packet loss, error rates, and correlations across multiple devices, providing meaningful inputs for anomaly detection. Vertex AI Prediction delivers low-latency anomaly detection, allowing immediate alerts and automated mitigation. Continuous retraining pipelines allow models to adapt to emerging failure patterns and changing network conditions, maintaining predictive accuracy. Autoscaling ensures efficient handling of peak log volumes. Logging, monitoring, and reproducibility provide operational reliability, traceability, and regulatory compliance. This architecture supports scalable, low-latency, and continuously adaptive network anomaly detection.

Storing logs in spreadsheets and manually identifying anomalies is impractical. Spreadsheets cannot efficiently process millions of log entries. Manual computation is slow, error-prone, and non-reproducible, making it unsuitable for operational monitoring.

Training a model once on historical logs and deploying it permanently is insufficient. Network conditions evolve, and static models cannot detect new anomalies, reducing detection accuracy and increasing operational risk. Continuous retraining and online feature computation are necessary for maintaining effectiveness.

The optimal solution is Pub/Sub for log ingestion, Dataflow for feature computation, and Vertex AI Prediction for online anomaly detection, providing scalable, low-latency, and continuously adaptive network monitoring.

Question 172

A bank wants to detect fraudulent transactions in real time for millions of customers. The system must scale to high transaction volumes, provide low-latency scoring, and continuously adapt to new fraud patterns. Which architecture is most appropriate?

A) Batch process transactions daily and manually review suspicious activity
B) Use Pub/Sub for transaction ingestion, Dataflow for feature computation, and Vertex AI Prediction for online fraud scoring
C) Store transactions in spreadsheets and manually compute fraud risk
D) Train a model once per year and deploy it permanently

Answer: B

Explanation:

Batch processing transactions daily and manually reviewing suspicious activity is inadequate for real-time fraud detection. Fraudulent transactions can occur within seconds, and daily batch processing introduces unacceptable delays, leaving fraudulent activity undetected. Manual review cannot scale to millions of transactions efficiently and is prone to human error. Batch workflows also do not allow continuous retraining, preventing models from adapting to evolving fraud patterns, reducing predictive accuracy over time. This approach fails to meet operational and security requirements for modern banking systems.

Using Pub/Sub for transaction ingestion, Dataflow for feature computation, and Vertex AI Prediction for online fraud scoring is the most appropriate solution. Pub/Sub ingests high-throughput transaction streams in real time, ensuring all transactions are captured without loss. Dataflow pipelines continuously compute derived features such as transaction frequency, location anomalies, device behavior, and spending patterns. Vertex AI Prediction provides low-latency fraud scoring, enabling immediate action on suspicious transactions. Continuous retraining pipelines allow models to adapt to emerging fraud tactics, improving predictive accuracy. Autoscaling ensures that high transaction volumes are handled efficiently. Logging, monitoring, and reproducibility provide operational reliability, auditability, and compliance with banking regulations. This architecture ensures scalable, low-latency, and continuously adaptive fraud detection for operational use.

Storing transactions in spreadsheets and manually computing fraud risk is impractical. Spreadsheets cannot efficiently process high-frequency, high-volume transaction data. Manual computation is slow, error-prone, non-reproducible, and unsuitable for operational monitoring or automated mitigation.

Training a model once per year and deploying it permanently is inadequate. Fraud patterns evolve rapidly, and a static model cannot adapt to new behavior, reducing accuracy and exposing the bank to financial risk. Continuous retraining and online scoring are necessary to maintain operational effectiveness.

The optimal solution is Pub/Sub for real-time ingestion, Dataflow for feature computation, and Vertex AI Prediction for online fraud scoring, providing scalable, low-latency, and continuously adaptive transaction monitoring.

Question 173

A logistics company wants to optimize delivery routes dynamically using real-time vehicle telemetry, traffic, and weather data. The system must scale to thousands of vehicles, provide low-latency recommendations, and continuously adapt to changing conditions. Which solution is most appropriate?

Answer: B

Explanation:

Batch processing, delivering, and traffic data daily, and manually updating routes daily, is insufficient for real-time route optimization. Traffic, vehicle availability, and weather conditions change continuously. Daily batch updates result in outdated recommendations, reducing efficiency and increasing delivery times. Manual computation cannot scale to thousands of vehicles and is error-prone. Batch workflows also lack continuous retraining, preventing adaptation to evolving patterns. This approach is unsuitable for enterprise logistics requiring low-latency, dynamic optimization.

Using Pub/Sub for real-time data ingestion, Dataflow for feature computation, and Vertex AI Prediction for online routing optimization is the most appropriate solution. Pub/Sub enables continuous ingestion of vehicle telemetry, traffic updates, and weather information. Dataflow pipelines compute derived features such as expected delays, congestion impact, and vehicle availability, which are essential for accurate routing. Vertex AI Prediction delivers low-latency recommendations to dispatch systems, enabling immediate adjustments to routes. Continuous retraining allows models to adapt to changing traffic patterns, vehicle behavior, and environmental factors. Autoscaling ensures efficient processing during peak delivery periods. Logging, monitoring, and reproducibility provide operational reliability, traceability, and governance compliance. This architecture supports scalable, low-latency, and continuously adaptive route optimization.

Storing vehicle and traffic data in spreadsheets and manually computing routes is impractical. Spreadsheets cannot process high-volume telemetry efficiently. Manual computation is slow, error-prone, non-reproducible, and unsuitable for continuous operational routing.

Training a route optimization model once and deploying it permanently is insufficient. Traffic, vehicle availability, and environmental conditions evolve constantly, and static models cannot adapt. Continuous retraining and online computation are necessary to maintain operational efficiency and accurate routing recommendations.

Question 174

A retailer wants to forecast demand for multiple products across hundreds of stores using historical sales, promotions, holidays, and weather. The system must scale to millions of records, allow feature reuse, and continuously update forecasts. Which solution is most appropriate?

Answer: B

Explanation:

Training separate models locally for each store using spreadsheets is impractical. Retail datasets include millions of records across hundreds of stores and multiple products, covering features such as historical sales, promotions, holidays, and weather. Local training cannot efficiently process this volume, and local workflows are slow, error-prone, and non-reproducible. Managing features separately for each store introduces redundancy and inconsistency. Automated retraining pipelines are difficult to implement locally, and feature reuse is limited. This approach is unsuitable for enterprise-level demand forecasting requiring scalability, automation, and accuracy.

Using Vertex AI Feature Store for centralized features and Vertex AI Training for distributed forecasting is the most appropriate solution. Feature Store ensures consistent, reusable features across multiple models, reducing duplication and ensuring training-serving consistency. Vertex AI Training supports distributed training across GPUs or TPUs, efficiently processing millions of historical records while capturing complex patterns in sales, promotions, holidays, and weather. Automated pipelines handle feature updates, retraining, and model versioning, ensuring forecasts continuously improve as new data becomes available. Autoscaling allows efficient handling of large datasets. Logging, monitoring, and experiment tracking provide reproducibility, operational reliability, and governance compliance. This architecture enables scalable, accurate, and continuously updated inventory demand forecasts across multiple stores and products.

Storing historical sales data in Cloud SQL and training a single global linear regression model is insufficient. Cloud SQL is not optimized for large-scale analytical workloads, and linear regression cannot capture complex non-linear relationships. A single global model may underfit and produce inaccurate forecasts, lacking localized precision.

The optimal solution is Vertex AI Feature Store combined with Vertex AI Training, providing scalable, reusable, and continuously updated inventory demand forecasts.

Question 175

A telecommunications company wants to predict network failures in real time using device logs. The system must scale to millions of log entries per second, provide low-latency alerts, and continuously adapt to evolving failure patterns. Which solution is most appropriate?

A) Batch process logs nightly and manually inspect for anomalies
B) Use Pub/Sub for log ingestion, Dataflow for feature computation, and Vertex AI Prediction for online anomaly detection
C) Store logs in spreadsheets and manually identify anomalies
D) Train a model once on historical logs and deploy permanently

Answer: B

Explanation:

Batch processing logs nightly and manually inspecting for anomalies is insufficient for real-time network failure prediction. Network conditions can deteriorate rapidly, and nightly batch processing introduces unacceptable delays, preventing timely detection. Manual inspection cannot scale to millions of log entries per second and is prone to error. Batch workflows also lack continuous retraining, which is necessary to adapt to new failure patterns and evolving device behavior. This approach is unsuitable for modern telecommunication operations that require real-time monitoring and rapid response to failures.

Using Pub/Sub for log ingestion, Dataflow for feature computation, and Vertex AI Prediction for online anomaly detection is the most appropriate solution. Pub/Sub provides high-throughput, real-time ingestion of device logs, ensuring that all events are captured without loss. Dataflow pipelines continuously compute derived features such as latency spikes, packet loss, error rates, and correlations across devices, providing meaningful inputs for anomaly detection models. Vertex AI Prediction delivers low-latency detection, enabling immediate alerts and automated mitigation actions. Continuous retraining pipelines allow models to adapt to emerging failure patterns and changing network conditions, maintaining predictive accuracy. Autoscaling ensures that high log volumes are processed efficiently. Logging, monitoring, and reproducibility provide operational reliability, traceability, and compliance with industry regulations. This architecture ensures scalable, low-latency, and continuously adaptive network failure detection.

Storing logs in spreadsheets and manually identifying anomalies is impractical. Spreadsheets cannot efficiently handle millions of log entries. Manual computation is slow, error-prone, and non-reproducible, making it unsuitable for operational monitoring.

Training a model once on historical logs and deploying permanently is insufficient. Network behavior evolves continuously, and static models cannot detect new anomalies or emerging failure patterns. Continuous retraining and online feature computation are necessary to maintain accurate detection and effective operational response.

Question 176

A bank wants to detect fraudulent credit card transactions in real time for millions of users. The system must scale to high transaction volumes, provide low-latency scoring, and continuously adapt to new fraud patterns. Which architecture is most appropriate?

Answer: B

Explanation:

Batch processing transactions daily and manually reviewing suspicious activity is insufficient for real-time fraud detection. Fraud can occur within seconds, and daily batch processing introduces delays that leave fraudulent activity undetected. Manual review cannot scale to millions of transactions efficiently and is prone to human error. Batch workflows also prevent continuous retraining, limiting the model’s ability to adapt to emerging fraud patterns, which reduces predictive accuracy over time. This approach fails to meet the operational requirements of modern banking systems that demand immediate fraud detection and prevention.

Using Pub/Sub for transaction ingestion, Dataflow for feature computation, and Vertex AI Prediction for online fraud scoring is the most appropriate solution. Pub/Sub enables high-throughput, real-time ingestion of credit card transactions, ensuring no events are missed. Dataflow pipelines compute derived features such as transaction frequency, location anomalies, device behavior, and spending patterns. Vertex AI Prediction provides low-latency scoring, enabling immediate detection and intervention. Continuous retraining pipelines allow models to adapt to new fraud patterns, maintaining accuracy over time. Autoscaling ensures high-volume transaction streams are handled efficiently. Logging, monitoring, and reproducibility provide operational reliability, auditability, and regulatory compliance. This architecture supports scalable, low-latency, and continuously adaptive fraud detection, providing operational resilience and real-time mitigation.

Training a model once per year and deploying permanently is inadequate. Fraud patterns evolve rapidly, and static models cannot detect new behaviors, leading to decreased accuracy and increased financial risk. Continuous retraining and online scoring are essential to maintain operational effectiveness.

Question 177

A retailer wants to forecast product demand across hundreds of stores using historical sales, promotions, holidays, and weather conditions. The system must scale to millions of records, allow feature reuse, and continuously update forecasts. Which solution is most appropriate?

Answer: B

Explanation:

Training separate models locally for each store using spreadsheets is impractical. Retail datasets include millions of records across hundreds of stores and multiple products, covering features such as historical sales, promotions, holidays, and weather. Local training cannot process this volume efficiently and is slow, error-prone, and non-reproducible. Managing features separately for each store introduces redundancy and inconsistency. Automated retraining pipelines are difficult to implement locally, and feature reuse is limited. This approach is unsuitable for enterprise-scale demand forecasting that requires accuracy, scalability, and automation.

Using Vertex AI Feature Store for centralized features and Vertex AI Training for distributed forecasting is the most appropriate solution. Feature Store ensures consistent, reusable features across multiple models, reducing duplication and ensuring consistency between training and serving. Vertex AI Training supports distributed training across GPUs or TPUs, efficiently processing millions of historical records while capturing complex patterns in sales, promotions, holidays, and weather. Automated pipelines handle feature updates, retraining, and model versioning, ensuring forecasts continuously improve as new data becomes available. Autoscaling allows efficient processing of large datasets. Logging, monitoring, and experiment tracking provide reproducibility, operational reliability, and governance compliance. This architecture enables scalable, accurate, and continuously updated inventory demand forecasts across multiple products and stores.

Using a simple rule-based system based on last year’s sales is inadequate. Rule-based systems cannot account for promotions, holidays, weather, or changing trends. They lack scalability, automation, and predictive accuracy, making them unsuitable for enterprise-level demand forecasting.

The optimal solution is Vertex AI Feature Store combined with Vertex AI Training, providing scalable, reusable, and continuously updated inventory demand forecasts.

Question 178

A healthcare provider wants to predict the likelihood of patient readmission using EHR data, lab results, and imaging. The system must comply with privacy regulations, scale to large datasets, and allow reproducible training pipelines. Which approach is most appropriate?

Answer: B

Explanation:

Downloading all patient data locally and training models manually is unsuitable due to privacy, compliance, and scalability issues. EHR data contains sensitive patient information regulated by HIPAA and other healthcare standards. Local storage increases the risk of unauthorized access, and manual training workflows are slow, error-prone, and non-reproducible. Local computation cannot efficiently handle heterogeneous datasets that include structured lab results and unstructured imaging data. Manual preprocessing introduces inconsistencies and prevents automated retraining, which is crucial for maintaining predictive accuracy. This approach fails to meet operational and regulatory requirements for secure healthcare analytics.

Using BigQuery for structured data, Cloud Storage for unstructured data, and Vertex AI Pipelines for preprocessing, training, and deployment is the most appropriate solution. BigQuery efficiently manages structured EHR data, enabling scalable querying of patient demographics, lab results, medication history, and vitals. Cloud Storage securely stores unstructured data such as imaging and clinical notes, allowing scalable and compliant access. Vertex AI Pipelines orchestrates preprocessing, feature extraction, training, and deployment in a reproducible manner, ensuring consistency and traceability. Continuous retraining pipelines allow models to adapt to new patient data, emerging treatments, and evolving clinical guidelines, maintaining predictive accuracy. Logging, monitoring, and experiment tracking ensure operational reliability, auditability, and privacy compliance. Autoscaling allows efficient processing of growing datasets. This architecture ensures secure, scalable, reproducible, and continuously adaptive readmission risk prediction.

Storing patient data in spreadsheets and manually computing readmission risk is impractical. Spreadsheets cannot handle large-scale structured and unstructured healthcare data. Manual computation is slow, error-prone, non-reproducible, and unsuitable for continuous operational prediction.

Training a model once using sample data and deploying it permanently is inadequate. Patient populations, treatments, and clinical protocols evolve. Static models cannot adapt to new patterns, resulting in reduced predictive accuracy. Continuous retraining and automated pipelines are essential for operational effectiveness.

Question 179

A logistics company wants to dynamically optimize delivery routes using real-time vehicle telemetry, traffic, and weather data. The system must scale to thousands of vehicles, provide low-latency recommendations, and continuously adapt to changing conditions. Which solution is most appropriate?

A) Batch process delivery and traffic data daily, and manually update routes
B) Use Pub/Sub for real-time data ingestion, Dataflow for feature computation, and Vertex AI Prediction for online route optimization
C) Store vehicle and traffic data in spreadsheets and manually compute routes
D) Train a route optimization model once and deploy it permanently

Answer: B

Explanation:

Batch processing, delivering, and traffic data daily, and manually updating routes is insufficient for real-time optimization. Traffic, vehicle availability, and weather conditions change continuously. Daily batch updates result in outdated recommendations, reducing delivery efficiency and customer satisfaction. Manual computation cannot scale to thousands of vehicles and is error-prone. Batch workflows also lack continuous retraining, preventing adaptation to changing patterns and reducing predictive accuracy. This approach is unsuitable for enterprise logistics requiring low-latency, dynamic routing optimization.

Using Pub/Sub for real-time data ingestion, Dataflow for feature computation, and Vertex AI Prediction for online route optimization is the most appropriate solution. Pub/Sub enables continuous ingestion of vehicle telemetry, traffic, and weather data, ensuring all updates are captured without loss. Dataflow pipelines compute derived features such as congestion impact, expected delays, and vehicle availability, providing inputs critical for accurate route recommendations. Vertex AI Prediction delivers low-latency route optimization, enabling immediate adjustments in dispatch operations. Continuous retraining pipelines allow models to adapt to evolving traffic patterns, vehicle behavior, and environmental conditions, ensuring recommendations remain accurate. Autoscaling allows efficient processing during peak delivery times. Logging, monitoring, and reproducibility provide operational reliability, traceability, and governance compliance. This architecture ensures scalable, low-latency, and continuously adaptive route optimization.

Storing vehicle and traffic data in spreadsheets and manually computing routes is impractical. Spreadsheets cannot process high-frequency telemetry efficiently. Manual computation is slow, error-prone, non-reproducible, and cannot support continuous operational updates.

Training a route optimization model once and deploying it permanently is insufficient. Traffic patterns, vehicle availability, and environmental factors evolve continuously. Static models cannot adapt, reducing efficiency. Continuous retraining and online computation are necessary for accurate and scalable route recommendations.

The optimal solution is Pub/Sub for ingestion, Dataflow for feature computation, and Vertex AI Prediction for online route optimization, providing scalable, low-latency, and continuously adaptive delivery recommendations.

Question 180

A retailer wants to forecast demand across hundreds of stores using historical sales, promotions, holidays, and weather. The system must scale to millions of records, allow feature reuse, and continuously update forecasts. Which solution is most appropriate?

Answer: B

Explanation:

Using Vertex AI Feature Store for centralized features and Vertex AI Training for distributed forecasting is the most appropriate solution. Feature Store ensures consistent, reusable features across multiple models, reducing duplication and ensuring training-serving consistency. Vertex AI Training supports distributed training across GPUs or TPUs, efficiently processing millions of historical records while capturing complex patterns in sales, promotions, holidays, and weather. Automated pipelines handle feature updates, retraining, and model versioning, ensuring forecasts continuously improve as new data becomes available. Autoscaling allows efficient processing of large datasets. Logging, monitoring, and experiment tracking provide reproducibility, operational reliability, and governance compliance. This architecture enables scalable, accurate, and continuously updated inventory demand forecasts across multiple stores and products.

The optimal solution is Vertex AI Feature Store combined with Vertex AI Training, providing scalable, reusable, and continuously updated inventory demand forecasts.

Google Professional Machine Learning Engineer Exam Dumps and Practice Test Questions Set 12 Q166-180

Related posts: