Question 780A recommendation system trains on files where key columns are missing after a supplier schema update. Which Google Cloud machine-learning design choice best satisfies the stated requirement? Use Agent Platform Model Registry plus a controlled approval step in the ML pipeline before production deployment. Use Managed Service for Apache Airflow orchestration when integration with existing governed DAG workflows is needed. Connect version-controlled data and code triggers to a managed training pipeline with recorded artifact and metric lineage. Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. ExplanationCorrect Answer D:Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. To validate the correction: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. Other Answers A:Registry governance separates successful training from authorization to expose a model in production. It does not resolve the specific failure; the targeted correction is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. B:Airflow manages DAG scheduling and dependencies across many services but does not remove task-level model evaluation needs. It does not resolve the specific failure; the targeted correction is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. C:Reproducible CI/CD/CT requires traceable inputs, durable build and training records and idempotent triggering. It does not resolve the specific failure; the targeted correction is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors.
Question 781A recommendation system trains on files where key columns are missing after a supplier schema update. Which underlying ML principle makes the proposed approach effective? Training-serving skew arises when logically equivalent features are computed with different code or fitted parameters. Retraining should be driven by meaningful quality change and valid fresh data, not solely a clock-based assumption. Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. Registry governance separates successful training from authorization to expose a model in production. ExplanationCorrect Answer C:Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. This supports the specific implementation: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. A suitable independent check is: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. Other Answers A:Training-serving skew arises when logically equivalent features are computed with different code or fitted parameters. The cause in the stated scenario is different: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. B:Retraining should be driven by meaningful quality change and valid fresh data, not solely a clock-based assumption. The cause in the stated scenario is different: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. D:Registry governance separates successful training from authorization to expose a model in production. The cause in the stated scenario is different: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models.
Question 782A recommendation system trains on files where key columns are missing after a supplier schema update. Which measurement or test should the team perform after implementation? Test that a deliberately inferior candidate remains staged while an approved candidate obtains a versioned release. Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure. Verify branch outputs, dependency order, failure handling and aggregate evaluation on representative regional data. Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. ExplanationCorrect Answer D:Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. This tests the underlying failure: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. Other Answers A:Continuous training creates candidate versions; deployment decisions need independent performance and safety evidence. That does not establish the required outcome; verify it by checking: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. B:Quality gates compare candidate evidence against policy before triggering a serving deployment. That does not establish the required outcome; verify it by checking: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. C:Directed acyclic pipeline graphs can run independent steps concurrently while waiting at synchronization dependencies. That does not establish the required outcome; verify it by checking: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report.
Question 783A recommendation system trains on files where key columns are missing after a supplier schema update. What governance or operational safeguard should accompany the implementation? Define metric, fairness and safety thresholds independently before viewing each candidate's test results. Require version-controlled pipeline definitions and explicit promotion gates for artifact quality and source integrity. Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. Predefine signoff responsibility and automatic rollback triggers for model-serving changes. ExplanationCorrect Answer C:Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. This protects the selected approach because Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. The immediate solution is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. Other Answers A:Quality gates compare candidate evidence against policy before triggering a serving deployment. The continuing safeguard required here is: Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. B:ML pipelines encode execution dependencies and artifacts so the same documented process can run consistently. The continuing safeguard required here is: Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. D:ML continuous delivery joins software deployment controls with model-specific validation and traffic management. The continuing safeguard required here is: Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds.
Question 784A credit predictor occasionally receives duplicate entity IDs that bias its training statistics. What should the team change to address the specific technical requirement? Build a versioned Agent Platform Pipeline with modular data checks, training, evaluation and registry tasks. Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. Enable safe component caching for deterministic inputs while enforcing invalidation when code or data digests change. Compare retraining candidates with a fixed evaluation protocol and promote only when they pass a production baseline gate. ExplanationCorrect Answer B:Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. To validate the correction: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. Other Answers A:ML pipelines encode execution dependencies and artifacts so the same documented process can run consistently. It does not resolve the specific failure; the targeted correction is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. C:Content-based caching can reuse previously computed artifacts when all declared inputs and implementation match. It does not resolve the specific failure; the targeted correction is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. D:Continuous training creates candidate versions; deployment decisions need independent performance and safety evidence. It does not resolve the specific failure; the targeted correction is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors.
Question 785A credit predictor occasionally receives duplicate entity IDs that bias its training statistics. Which underlying ML principle makes the proposed approach effective? Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. Content-based caching can reuse previously computed artifacts when all declared inputs and implementation match. Retraining should be driven by meaningful quality change and valid fresh data, not solely a clock-based assumption. Registry governance separates successful training from authorization to expose a model in production. ExplanationCorrect Answer A:Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. This supports the specific implementation: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. A suitable independent check is: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. Other Answers B:Content-based caching can reuse previously computed artifacts when all declared inputs and implementation match. The cause in the stated scenario is different: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. C:Retraining should be driven by meaningful quality change and valid fresh data, not solely a clock-based assumption. The cause in the stated scenario is different: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. D:Registry governance separates successful training from authorization to expose a model in production. The cause in the stated scenario is different: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models.
Question 786A credit predictor occasionally receives duplicate entity IDs that bias its training statistics. What is the most relevant acceptance check for the proposed ML change? Simulate a scheduled run and ensure the new artifact is rejected if held-out metrics deteriorate. Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. Verify branch outputs, dependency order, failure handling and aggregate evaluation on representative regional data. Compare cache hits across identical reruns and verify a changed source snapshot forces component reexecution. ExplanationCorrect Answer B:Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. This tests the underlying failure: Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. Other Answers A:Scheduled retraining provides predictable refreshes but still requires quality checks before production promotion. That does not establish the required outcome; verify it by checking: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. C:Directed acyclic pipeline graphs can run independent steps concurrently while waiting at synchronization dependencies. That does not establish the required outcome; verify it by checking: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report. D:Content-based caching can reuse previously computed artifacts when all declared inputs and implementation match. That does not establish the required outcome; verify it by checking: Inject a malformed fixture and confirm the pipeline blocks training with an actionable quality report.
Question 787A credit predictor occasionally receives duplicate entity IDs that bias its training statistics. What governance or operational safeguard should accompany the implementation? Enforce separation of duties and immutable provenance evidence for production model approvals. Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. Require transformation-digest and schema-parity tests in every pipeline promotion review. Require branch protection, dependency scanning and image-signature verification in the build policy. ExplanationCorrect Answer B:Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. This protects the selected approach because Automated data validation prevents invalid distributions and schema changes from silently contaminating downstream models. The immediate solution is: Add automated data-schema and quality checks before model training, with a fail-closed policy for material errors. Other Answers A:Registry governance separates successful training from authorization to expose a model in production. The continuing safeguard required here is: Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. C:Training-serving skew arises when logically equivalent features are computed with different code or fitted parameters. The continuing safeguard required here is: Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds. D:Continuous integration converts source changes into reproducible artifacts but cannot establish model quality on its own. The continuing safeguard required here is: Version allowed data contracts and monitor recurring validation failures before relaxing any acceptance thresholds.
Question 788A new model performs worse than the production baseline but the pipeline still deploys it automatically. What should the team change to address the specific technical requirement? Use Agent Platform Model Registry plus a controlled approval step in the ML pipeline before production deployment. Schedule regular retraining with approved snapshots and validation in the managed pipeline scheduler. Add an explicit evaluation and approval component that blocks promotion unless documented acceptance thresholds pass. Build a versioned Agent Platform Pipeline with modular data checks, training, evaluation and registry tasks. ExplanationCorrect Answer C:Quality gates compare candidate evidence against policy before triggering a serving deployment. To validate the correction: Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure. Other Answers A:Registry governance separates successful training from authorization to expose a model in production. It does not resolve the specific failure; the targeted correction is: Add an explicit evaluation and approval component that blocks promotion unless documented acceptance thresholds pass. B:Scheduled retraining provides predictable refreshes but still requires quality checks before production promotion. It does not resolve the specific failure; the targeted correction is: Add an explicit evaluation and approval component that blocks promotion unless documented acceptance thresholds pass. D:ML pipelines encode execution dependencies and artifacts so the same documented process can run consistently. It does not resolve the specific failure; the targeted correction is: Add an explicit evaluation and approval component that blocks promotion unless documented acceptance thresholds pass.
Question 789A new model performs worse than the production baseline but the pipeline still deploys it automatically. Which technical mechanism is most relevant to this outcome? Quality gates compare candidate evidence against policy before triggering a serving deployment. Airflow manages DAG scheduling and dependencies across many services but does not remove task-level model evaluation needs. Content-based caching can reuse previously computed artifacts when all declared inputs and implementation match. Reproducible CI/CD/CT requires traceable inputs, durable build and training records and idempotent triggering. ExplanationCorrect Answer A:Quality gates compare candidate evidence against policy before triggering a serving deployment. This supports the specific implementation: Add an explicit evaluation and approval component that blocks promotion unless documented acceptance thresholds pass. A suitable independent check is: Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure. Other Answers B:Airflow manages DAG scheduling and dependencies across many services but does not remove task-level model evaluation needs. The cause in the stated scenario is different: Quality gates compare candidate evidence against policy before triggering a serving deployment. C:Content-based caching can reuse previously computed artifacts when all declared inputs and implementation match. The cause in the stated scenario is different: Quality gates compare candidate evidence against policy before triggering a serving deployment. D:Reproducible CI/CD/CT requires traceable inputs, durable build and training records and idempotent triggering. The cause in the stated scenario is different: Quality gates compare candidate evidence against policy before triggering a serving deployment.
Question 790A new model performs worse than the production baseline but the pipeline still deploys it automatically. What is the most relevant acceptance check for the proposed ML change? Test that a deliberately inferior candidate remains staged while an approved candidate obtains a versioned release. Confirm unapproved versions cannot deploy and approved versions record actor, artifact digest and evaluation report. Trigger the pipeline with a fixed dataset and inspect component states, lineage, model metrics and generated registry entry. Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure. ExplanationCorrect Answer D:Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure. This tests the underlying failure: Quality gates compare candidate evidence against policy before triggering a serving deployment. Other Answers A:Continuous training creates candidate versions; deployment decisions need independent performance and safety evidence. That does not establish the required outcome; verify it by checking: Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure. B:Registry governance separates successful training from authorization to expose a model in production. That does not establish the required outcome; verify it by checking: Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure. C:ML pipelines encode execution dependencies and artifacts so the same documented process can run consistently. That does not establish the required outcome; verify it by checking: Run a deliberately poor candidate and verify that no serving-version change occurs after evaluation failure.