Question 640A document classifier is deployed without the tokenizer version used during its training run. What is the most relevant acceptance check for the proposed ML change? Inject malformed and unsafe test outputs and check parser rejection, redaction and safe fallback paths. Replay the same raw test records through training and serving and compare transformed tensor values and outputs. Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Confirm approved services can score requests over expected private paths and unauthorized callers are denied. ExplanationCorrect Answer B:Replay the same raw test records through training and serving and compare transformed tensor values and outputs. This tests the underlying failure: Training-serving feature skew can arise when model inputs are transformed inconsistently across environments. Other Answers A:Generative model outputs are probabilistic and require application validation before they can safely drive deterministic systems. That does not establish the required outcome; verify it by checking: Replay the same raw test records through training and serving and compare transformed tensor values and outputs. C:Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. That does not establish the required outcome; verify it by checking: Replay the same raw test records through training and serving and compare transformed tensor values and outputs. D:Endpoint network reachability and cloud identity authorization are separate security boundaries. That does not establish the required outcome; verify it by checking: Replay the same raw test records through training and serving and compare transformed tensor values and outputs.
Question 641A document classifier is deployed without the tokenizer version used during its training run. What preventive release checklist item best protects the intended outcome? Require a documented latency justification before reserving always-on warm serving resources. Make preprocessing parity and schema-contract checks mandatory in model rollout pipelines. Record framework version and image compatibility tests for each model release. Scan images, pin dependencies and test cold starts before releasing custom serving containers. ExplanationCorrect Answer B:Make preprocessing parity and schema-contract checks mandatory in model rollout pipelines. This protects the selected approach because Training-serving feature skew can arise when model inputs are transformed inconsistently across environments. The immediate solution is: Package and version inference preprocessing and postprocessing together with the approved model artifact. Other Answers A:Warm replicas reduce first-request initialization latency but incur charges while receiving no traffic. The continuing safeguard required here is: Make preprocessing parity and schema-contract checks mandatory in model rollout pipelines. C:Supported prebuilt serving environments reduce runtime management but depend on matching artifact formats and versions. The continuing safeguard required here is: Make preprocessing parity and schema-contract checks mandatory in model rollout pipelines. D:A custom container controls dependencies and request handling but inherits security, compatibility and patching duties. The continuing safeguard required here is: Make preprocessing parity and schema-contract checks mandatory in model rollout pipelines.
Question 642A small stateless inference application has bursty traffic and should scale to zero between requests. What should the team change to address the specific technical requirement? Prefer a compatible managed prebuilt inference container over building custom infrastructure when it meets requirements. Profile per-request token generation, model size and decoding settings before scaling only the replica count. Split production traffic between approved old and new model versions using a monitored canary rollout. Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. ExplanationCorrect Answer D:Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. To validate the correction: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Other Answers A:Supported prebuilt serving environments reduce runtime management but depend on matching artifact formats and versions. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. B:Horizontal scaling raises concurrent capacity but does not necessarily accelerate computation within an individual inference request. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. C:Canary traffic allocation limits the initial exposure of a new model while collecting live performance evidence. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed.
Question 643A small stateless inference application has bursty traffic and should scale to zero between requests. Which underlying ML principle makes the proposed approach effective? Endpoint network reachability and cloud identity authorization are separate security boundaries. Batch prediction amortizes job start overhead across large datasets and avoids always-on serving resources. Randomized model assignment estimates causal effects more reliably than comparing different uncontrolled traffic windows. Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. ExplanationCorrect Answer D:Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. This supports the specific implementation: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. A suitable independent check is: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Other Answers A:Endpoint network reachability and cloud identity authorization are separate security boundaries. The cause in the stated scenario is different: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. B:Batch prediction amortizes job start overhead across large datasets and avoids always-on serving resources. The cause in the stated scenario is different: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. C:Randomized model assignment estimates causal effects more reliably than comparing different uncontrolled traffic windows. The cause in the stated scenario is different: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter.
Question 644A small stateless inference application has bursty traffic and should scale to zero between requests. What is the most relevant acceptance check for the proposed ML change? Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Compare per-request cost, p95 latency, memory saturation and measured throughput across hardware configurations. Trace a served version back to its training run and verify a controlled rollback restores previous behavior. Verify complete output row counts, cost per prediction and batch completion within the required business window. ExplanationCorrect Answer A:Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. This tests the underlying failure: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. Other Answers B:Hardware acceleration is beneficial only when supported operators and workload intensity justify the resource premium. That does not establish the required outcome; verify it by checking: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. C:Model registry versioning connects a deployable model to metadata, approval and rollback history. That does not establish the required outcome; verify it by checking: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. D:Batch prediction amortizes job start overhead across large datasets and avoids always-on serving resources. That does not establish the required outcome; verify it by checking: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior.
Question 645A small stateless inference application has bursty traffic and should scale to zero between requests. What governance or operational safeguard should accompany the implementation? Maintain schema tests and safety filters as versioned components of the inference service. Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. Review endpoint exposure and identity policies before enabling any new inference consumer. Record framework version and image compatibility tests for each model release. ExplanationCorrect Answer B:Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. This protects the selected approach because Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. The immediate solution is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. Other Answers A:Generative model outputs are probabilistic and require application validation before they can safely drive deterministic systems. The continuing safeguard required here is: Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. C:Endpoint network reachability and cloud identity authorization are separate security boundaries. The continuing safeguard required here is: Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. D:Supported prebuilt serving environments reduce runtime management but depend on matching artifact formats and versions. The continuing safeguard required here is: Monitor cold starts and cost per request and document when dedicated model endpoints become necessary.
Question 646A custom containerized text classifier has intermittent demand and does not need dedicated accelerator capacity. What should the team change to address the specific technical requirement? Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. Register versioned model artifacts in Gemini Enterprise Agent Platform Model Registry and deploy approved versions by ID. Run a randomized A/B test with stable assignment, clear primary metrics and sufficient sample duration. Deploy a suitably optimized edge model and establish controlled synchronization and rollout mechanisms. ExplanationCorrect Answer A:Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. To validate the correction: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Other Answers B:Model registry versioning connects a deployable model to metadata, approval and rollback history. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. C:Randomized model assignment estimates causal effects more reliably than comparing different uncontrolled traffic windows. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. D:Edge inference trades centralized elasticity for local latency and offline availability with hardware constraints. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed.
Question 647A custom containerized text classifier has intermittent demand and does not need dedicated accelerator capacity. Which property of the selected ML workflow accounts for this requirement? Canary traffic allocation limits the initial exposure of a new model while collecting live performance evidence. Batching increases parallel accelerator use but adds queueing delay and may harm tail latency if configured poorly. Model registry versioning connects a deployable model to metadata, approval and rollback history. Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. ExplanationCorrect Answer D:Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. This supports the specific implementation: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. A suitable independent check is: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Other Answers A:Canary traffic allocation limits the initial exposure of a new model while collecting live performance evidence. The cause in the stated scenario is different: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. B:Batching increases parallel accelerator use but adds queueing delay and may harm tail latency if configured poorly. The cause in the stated scenario is different: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. C:Model registry versioning connects a deployable model to metadata, approval and rollback history. The cause in the stated scenario is different: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter.
Question 648A custom containerized text classifier has intermittent demand and does not need dedicated accelerator capacity. Which measurement or test should the team perform after implementation? Run smoke and load tests against the container image digest and confirm readiness and error handling. Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Deploy a test artifact and confirm request schema, predictions and runtime library compatibility. Compare batch-size distribution, throughput, GPU utilization and p99 latency under realistic request mixes. ExplanationCorrect Answer B:Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. This tests the underlying failure: Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. Other Answers A:A custom container controls dependencies and request handling but inherits security, compatibility and patching duties. That does not establish the required outcome; verify it by checking: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. C:Supported prebuilt serving environments reduce runtime management but depend on matching artifact formats and versions. That does not establish the required outcome; verify it by checking: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. D:Batching increases parallel accelerator use but adds queueing delay and may harm tail latency if configured poorly. That does not establish the required outcome; verify it by checking: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior.
Question 649A custom containerized text classifier has intermittent demand and does not need dedicated accelerator capacity. Which ongoing standard would make this result reliable for future model versions? Record framework version and image compatibility tests for each model release. Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. Define endpoint SLOs, capacity limits and rollback ownership before exposing production traffic. Define signed model-update, rollback and device-monitoring policies for remote edge deployments. ExplanationCorrect Answer B:Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. This protects the selected approach because Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. The immediate solution is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. Other Answers A:Supported prebuilt serving environments reduce runtime management but depend on matching artifact formats and versions. The continuing safeguard required here is: Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. C:Online prediction keeps inference capacity available for request-response workloads at the cost of capacity management. The continuing safeguard required here is: Monitor cold starts and cost per request and document when dedicated model endpoints become necessary. D:Edge inference trades centralized elasticity for local latency and offline availability with hardware constraints. The continuing safeguard required here is: Monitor cold starts and cost per request and document when dedicated model endpoints become necessary.
Question 650A startup requires a serverless prediction API for a lightweight CPU-based model with modest cold-start tolerance. What should the team change to address the specific technical requirement? Package and version inference preprocessing and postprocessing together with the approved model artifact. Choose serving accelerator memory and concurrency limits based on measured token or batch demand. Run a randomized A/B test with stable assignment, clear primary metrics and sufficient sample duration. Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. ExplanationCorrect Answer D:Cloud Run scales container services with requests and may reduce idle cost, though cold starts and resource limits matter. To validate the correction: Test first-request latency, sustained throughput, request authentication and scale-to-zero behavior. Other Answers A:Training-serving feature skew can arise when model inputs are transformed inconsistently across environments. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. B:Generative inference memory depends on model parameters, KV-cache and concurrent sequence lengths, not only average CPU use. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed. C:Randomized model assignment estimates causal effects more reliably than comparing different uncontrolled traffic windows. It does not resolve the specific failure; the targeted correction is: Evaluate Cloud Run container serving and configure concurrency, authentication and minimum instances as needed.