professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
A data engineering team is deploying automated machine learning pipelines with BigQuery ML and Vertex AI. To satisfy strict governance and reproducibility requirements across iterative model runs, the team must implement an architecture that:
Which combination of Google Cloud services and practices should the team implement?
Capture training data versions using BigQuery table snapshots, log experiment parameters and dataset-to-model lineage in Vertex ML Metadata via Vertex AI Experiments, and detect skew between serving features and training baselines using ML.VALIDATE_DATA_SKEW.
Export training datasets to timestamped Cloud Storage CSV files, track pipeline executions using custom Cloud Logging metrics, and use ML.DESCRIBE_DATA to automatically generate real-time alerts for serving skew.
Query live training records via standard BigQuery views, version pipeline source code and runtime parameters in Artifact Registry, and compare serving batches against historical serving data using ML.VALIDATE_DATA_DRIFT.
Materialize dynamic BigLake tables for each pipeline run, store hyperparameter configurations in Vertex AI Feature Store, and use Vertex Explainable AI feature attributions as the sole mechanism to block data distribution anomalies.
Capture training data versions using BigQuery table snapshots, log experiment parameters and dataset-to-model lineage in Vertex ML Metadata via Vertex AI Experiments, and detect skew between serving features and training baselines using ML.VALIDATE_DATA_SKEW.
This architecture combines BigQuery table snapshots, Vertex ML Metadata (integrated through Vertex AI Experiments), and native BigQuery ML monitoring functions like ML.VALIDATE_DATA_SKEW to build a complete, reproducible, and verifiable ML lifecycle.
StudyCerts
StudyCertsML.VALIDATE_DATA_SKEW function compares incoming production serving data against these precomputed training statistics to detect distribution shifts without requiring raw training data reloading.Combining native table snapshots with managed ML metadata and precomputed statistical skew evaluation provides a fully integrated, enterprise-grade MLOps workflow without custom infrastructure overhead.
Export training datasets to timestamped Cloud Storage CSV files, track pipeline executions using custom Cloud Logging metrics, and use ML.DESCRIBE_DATA to automatically generate real-time alerts for serving skew.
Query live training records via standard BigQuery views, version pipeline source code and runtime parameters in Artifact Registry, and compare serving batches against historical serving data using ML.VALIDATE_DATA_DRIFT.
Materialize dynamic BigLake tables for each pipeline run, store hyperparameter configurations in Vertex AI Feature Store, and use Vertex Explainable AI feature attributions as the sole mechanism to block data distribution anomalies.