Google Professional Machine Learning Engineer Practice Test 69
Question 680
During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: A team imports a pretrained JAX checkpoint in a notebook but assumes its model weights and device setup will load unchanged in a PyTorch-only runtime. The handoff must preserve privacy, lineage and testable behavior. Which TWO selections represent the correct investigation and remediation together? Select TWO.
- Push aggregations into BigQuery or stream bounded samples to the notebook rather than materializing the whole table.
- Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training.
- Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths.
- Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA.
- Restart the runtime, run the notebook top to bottom and compare variable initialization with committed source revision.
Explanation
Correct Answers
B:Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training. This is the targeted corrective response for model garden jax accelerator compatibility. Framework-native checkpoints and runtime APIs are not automatically interchangeable across ML libraries. Verify the diagnosis using: Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. Confirm success using: A clean notebook loads the exact model revision, runs representative inputs and reports consistent outputs. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….
C:Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. This inspects evidence relevant to model garden jax accelerator compatibility. Framework-native checkpoints and runtime APIs are not automatically interchangeable across ML libraries. After identifying the cause, the matching correction is: Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….
Incorrect Answers
A:Push aggregations into BigQuery or stream bounded samples to the notebook rather than materializing the whole table. This is an action or diagnostic relevant to notebook memory exhaustion on full data extraction, not one of the required two steps. In this scenario verify: Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. Then correct: Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training.
D:Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA. This is an action or diagnostic relevant to bigquery versus dataflow preparation selection, not one of the required two steps. In this scenario verify: Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. Then correct: Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training.
E:Restart the runtime, run the notebook top to bottom and compare variable initialization with committed source revision. This is an action or diagnostic relevant to notebook transient state and execution order, not one of the required two steps. In this scenario verify: Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. Then correct: Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training.
Question 681
During a production ML inference release on Google Cloud, the following condition occurs: A public prediction API queues unbounded client retries during a traffic spike, creating a cascading latency and memory outage. The service must meet its agreed quality and latency requirements. Which configuration or procedure is the most appropriate correction?
- Pin releases to reviewed immutable image digests and record image plus model artifact versions.
- Test a supported post-training quantization or optimization path and release only if target quality remains acceptable.
- Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses.
- Schedule and monitor approved Feature Store synchronization at the needed frequency, with stale-feature handling.
Explanation
Correct Answer
C:Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses. This is the targeted corrective response for predictive serving rate limit and backpressure. Unlimited retries amplify overload; backpressure and controlled concurrency are needed along with scaling. Verify the diagnosis using: Inspect quota errors, retry behavior, queue occupancy, tail latency and autoscaling upper limits. Confirm success using: Peak traffic is rate-limited predictably and the serving fleet recovers without an unbounded request backlog. This matters here because a public prediction API queues unbounded client retries during a traffic spike, creating a cascading latency and….
Incorrect Answers
A:Pin releases to reviewed immutable image digests and record image plus model artifact versions. This action addresses model artifact image digest reproducibility, not the failure in the described predictive serving rate limit and backpressure case. The targeted correction is: Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses.
B:Test a supported post-training quantization or optimization path and release only if target quality remains acceptable. This action addresses inference optimization using quantization, not the failure in the described predictive serving rate limit and backpressure case. The targeted correction is: Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses.
D:Schedule and monitor approved Feature Store synchronization at the needed frequency, with stale-feature handling. This action addresses feature store freshness and online sync, not the failure in the described predictive serving rate limit and backpressure case. The targeted correction is: Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses.
Question 682
As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A public conversational app relies on a single instruction asking the model to avoid prohibited content but does not test or screen generated responses. The fix must retain legitimate model usefulness and appropriate controls. Which TWO complementary choices jointly establish the evidence and appropriate correction? Select TWO.
- Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers.
- Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.
- Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims.
- Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow.
- Review the business safety taxonomy, representative adversarial evaluation prompts, safety-filter configuration and escalation design.
Explanation
Correct Answers
B:Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results. This is the targeted corrective response for gen ai output safety policy enforcement. Prompt wording alone is not a reliable comprehensive safety boundary for public generative applications. Verify the diagnosis using: Review the business safety taxonomy, representative adversarial evaluation prompts, safety-filter configuration and escalation design. Confirm success using: Red-team test prompts trigger expected safeguards while legitimate requests continue to receive useful responses.
E:Review the business safety taxonomy, representative adversarial evaluation prompts, safety-filter configuration and escalation design. This inspects evidence relevant to gen ai output safety policy enforcement. Prompt wording alone is not a reliable comprehensive safety boundary for public generative applications. After identifying the cause, the matching correction is: Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.
Incorrect Answers
A:Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers. This is an action or diagnostic relevant to training data exfiltration through broad access, not one of the required two steps. In this scenario verify: Review the business safety taxonomy, representative adversarial evaluation prompts, safety-filter configuration and escalation design. Then correct: Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.
C:Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims. This is an action or diagnostic relevant to explainability versus causal claim, not one of the required two steps. In this scenario verify: Review the business safety taxonomy, representative adversarial evaluation prompts, safety-filter configuration and escalation design. Then correct: Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.
D:Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow. This is an action or diagnostic relevant to training-serving feature skew detection, not one of the required two steps. In this scenario verify: Review the business safety taxonomy, representative adversarial evaluation prompts, safety-filter configuration and escalation design. Then correct: Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.
Question 683
During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A retailer has no trustworthy segment labels but attempts a supervised classifier with synthetic classes supplied by the sales team. The owners require measurable quality and controlled operating cost. What implementation change resolves the specific issue without substituting an unrelated fix?
- Use a suitable ARIMA_PLUS time-series model with timestamp and data columns and evaluate ML.FORECAST on rolling historical cutoffs.
- Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
- Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates.
- Evaluate Agent Platform AutoML tabular training against a simple baseline and select it if quality and operating cost justify the managed path.
Explanation
Correct Answer
B:Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability. This is the targeted corrective response for bigquery ml kmeans customer segmentation. K-means discovers unlabeled similarity groups; fabricating labels would make supervised accuracy meaningless. Verify the diagnosis using: Check whether real class labels exist and examine the standardized input distributions and cluster stability under different seeds. Confirm success using: Stable clusters reveal coherent customer behavior without pretending an unsupervised assignment is known supervised ground truth.
Incorrect Answers
A:Use a suitable ARIMA_PLUS time-series model with timestamp and data columns and evaluate ML.FORECAST on rolling historical cutoffs. This action addresses bigquery arima_plus forecast horizon, not the failure in the described bigquery ml kmeans customer segmentation case. The targeted correction is: Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
C:Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates. This action addresses model garden task and license selection, not the failure in the described bigquery ml kmeans customer segmentation case. The targeted correction is: Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
D:Evaluate Agent Platform AutoML tabular training against a simple baseline and select it if quality and operating cost justify the managed path. This action addresses automl tabular supervised model selection, not the failure in the described bigquery ml kmeans customer segmentation case. The targeted correction is: Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
Question 684
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A product search team trains a binary spam classifier to find the most semantically relevant help article for a free-text question. Engineers need an auditable, resource-aware correction to the issue. What implementation change resolves the specific issue without substituting an unrelated fix?
- Benchmark compatible TPU and GPU configurations and select hardware based on measured throughput and target budget.
- Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.
- Choose a decision threshold using acceptable recall and alert burden with a validated independent cohort.
- Use supported structured output and schema validation with graceful retry or rejection for nonconforming responses.
Explanation
Correct Answer
B:Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision. This is the targeted corrective response for embedding retrieval versus text classifier. A binary classifier assigns predefined labels; semantic search needs query-to-document relevance ranking. Verify the diagnosis using: Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples. Confirm success using: Relevant articles rank highly for unseen paraphrased queries and retrieval hit rate is measured against judgments.
Incorrect Answers
A:Benchmark compatible TPU and GPU configurations and select hardware based on measured throughput and target budget. This action addresses tpu versus gpu for tensorflow workload, not the failure in the described embedding retrieval versus text classifier case. The targeted correction is: Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.
C:Choose a decision threshold using acceptable recall and alert burden with a validated independent cohort. This action addresses cost-sensitive threshold for rare positives, not the failure in the described embedding retrieval versus text classifier case. The targeted correction is: Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.
D:Use supported structured output and schema validation with graceful retry or rejection for nonconforming responses. This action addresses constrained generative json outputs, not the failure in the described embedding retrieval versus text classifier case. The targeted correction is: Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.
Question 685
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: An engineer runs an unbounded grid across learning rates, depths and regularization values, using expensive accelerators without a metric-driven stopping rule. Engineers need an auditable, resource-aware correction to the issue. Which configuration or procedure is the most appropriate correction?
- Recompute lagged windows using only prior observations and validate with rolling-origin splits.
- Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.
- Request justified quota or select an available compatible accelerator and region without compromising data residency controls.
- Use licensed and permitted training images with appropriate governance reviews before any supported tuning job.
Explanation
Correct Answer
B:Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping. This is the targeted corrective response for hyperparameter search budget limit. Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost. Verify the diagnosis using: Review parameter ranges, total trial count, training budget and the metric used to rank completed experiments. Confirm success using: Trials stay within the approved compute budget and a winner improves the specified independent metric.
Incorrect Answers
A:Recompute lagged windows using only prior observations and validate with rolling-origin splits. This action addresses temporal training label leakage in rolling windows, not the failure in the described hyperparameter search budget limit case. The targeted correction is: Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.
C:Request justified quota or select an available compatible accelerator and region without compromising data residency controls. This action addresses accelerator quota and regional availability, not the failure in the described hyperparameter search budget limit case. The targeted correction is: Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.
D:Use licensed and permitted training images with appropriate governance reviews before any supported tuning job. This action addresses fine-tuning image generator data rights, not the failure in the described hyperparameter search budget limit case. The targeted correction is: Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.
Question 686
During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A policy assistant's answers become stale every week when procedures change, and engineers repeatedly fine-tune the base model to incorporate each revision. The owners require measurable quality and controlled operating cost. Select TWO: the decisive diagnostic step and the targeted repair for this specific issue.
- Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation.
- Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task.
- Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy.
- Use ML.PREDICT on the appropriate BigQuery ML model within a controlled SQL batch job, writing results to governed tables.
- Benchmark a supported lower-latency Gemini variant against the current model under representative traffic before routing requests.
Explanation
Correct Answers
A:Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation. This is the targeted corrective response for foundation model tuning versus retrieval update. Frequently changing external knowledge is better supplied through current context than repeatedly embedded into model weights. Verify the diagnosis using: Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy. Confirm success using: A revised policy becomes answerable after document indexing without retraining, and retrieved citations match the active version. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
C:Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy. This inspects evidence relevant to foundation model tuning versus retrieval update. Frequently changing external knowledge is better supplied through current context than repeatedly embedded into model weights. After identifying the cause, the matching correction is: Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
Incorrect Answers
B:Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task. This is an action or diagnostic relevant to model garden task and license selection, not one of the required two steps. In this scenario verify: Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy. Then correct: Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation.
D:Use ML.PREDICT on the appropriate BigQuery ML model within a controlled SQL batch job, writing results to governed tables. This is an action or diagnostic relevant to bigquery ml sql batch prediction integration, not one of the required two steps. In this scenario verify: Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy. Then correct: Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation.
E:Benchmark a supported lower-latency Gemini variant against the current model under representative traffic before routing requests. This is an action or diagnostic relevant to gemini model choice for latency versus complexity, not one of the required two steps. In this scenario verify: Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy. Then correct: Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
Question 687
During model-training validation on a Google Cloud experimental project, the following condition occurs: A custom training image expects a local CSV under the developer's home directory but managed training supplies data through configured Cloud Storage paths. The change should preserve a meaningful independent model-quality comparison. Which evidence most directly establishes what is wrong with this AI or ML workflow?
- Inspect feature computation cutoffs, window frame bounds, label timestamps and time-aware evaluation splits.
- Inspect GPU memory traces, activation tensor sizes, batch size, optimizer state and training failure logs.
- Inspect task input configuration, container logs, expected file patterns and staged object paths.
- Inspect time stamps, autocorrelation, horizon, seasonal cycles and out-of-sample forecast metrics against traditional baselines.
Explanation
Correct Answer
C:Inspect task input configuration, container logs, expected file patterns and staged object paths. This inspects evidence relevant to custom training input schema mismatch. Notebook filesystem locations are not portable contracts for managed container training jobs. After identifying the cause, the matching correction is: Adapt the training program to the managed data input contract or stage files to an explicit configurable path.
Incorrect Answers
A:Inspect feature computation cutoffs, window frame bounds, label timestamps and time-aware evaluation splits. This examines temporal training label leakage in rolling windows rather than the specific mechanism reported here. It is not the decisive first check for custom training input schema mismatch. The relevant evidence is: Inspect task input configuration, container logs, expected file patterns and staged object paths.
B:Inspect GPU memory traces, activation tensor sizes, batch size, optimizer state and training failure logs. This examines gpu out-of-memory batch control rather than the specific mechanism reported here. It is not the decisive first check for custom training input schema mismatch. The relevant evidence is: Inspect task input configuration, container logs, expected file patterns and staged object paths.
D:Inspect time stamps, autocorrelation, horizon, seasonal cycles and out-of-sample forecast metrics against traditional baselines. This examines forecast trend and seasonality versus llm rather than the specific mechanism reported here. It is not the decisive first check for custom training input schema mismatch. The relevant evidence is: Inspect task input configuration, container logs, expected file patterns and staged object paths.
Question 688
During model-training validation on a Google Cloud experimental project, the following condition occurs: A transformer cannot fit its weights and activations on one device even at minimal batch size, but the team proposes more data replicas only. The change should preserve a meaningful independent model-quality comparison. Which statement identifies the primary reason for this failure?
- An accelerator can sit idle waiting for input even when its own memory and compute capacity are sufficient.
- Data parallel replicas each hold a model copy; they do not solve a model-too-large-for-one-device problem.
- Prompt-only requests for JSON may not guarantee type validity; interface contracts need machine-verifiable constraints.
- Distributed speedups depend on communication-to-compute ratio, not merely the number of accelerators allocated.
Explanation
Correct Answer
B:Data parallel replicas each hold a model copy; they do not solve a model-too-large-for-one-device problem. This explains the mechanism behind model parallelism for memory-bound transformer and why the described failure is possible. A discriminating investigation is: Inspect parameter and activation memory per device, optimizer memory and available interconnect bandwidth. The corresponding repair is: Evaluate supported tensor or pipeline model parallelism to split the model across compatible accelerators.
Incorrect Answers
A:An accelerator can sit idle waiting for input even when its own memory and compute capacity are sufficient. This principle describes accelerator starvation from slow input pipeline, which is not the cause of the observed model parallelism for memory-bound transformer failure. The controlling explanation is: Data parallel replicas each hold a model copy; they do not solve a model-too-large-for-one-device problem.
C:Prompt-only requests for JSON may not guarantee type validity; interface contracts need machine-verifiable constraints. This principle describes constrained generative json outputs, which is not the cause of the observed model parallelism for memory-bound transformer failure. The controlling explanation is: Data parallel replicas each hold a model copy; they do not solve a model-too-large-for-one-device problem.
D:Distributed speedups depend on communication-to-compute ratio, not merely the number of accelerators allocated. This principle describes distributed gradient communication bottleneck, which is not the cause of the observed model parallelism for memory-bound transformer failure. The controlling explanation is: Data parallel replicas each hold a model copy; they do not solve a model-too-large-for-one-device problem.
Question 689
During a production ML inference release on Google Cloud, the following condition occurs: A text embedding model cannot fit into a chosen tiny GPU's memory, but a team only considers increasing container CPU cores. The service must meet its agreed quality and latency requirements. Which TWO complementary choices jointly establish the evidence and appropriate correction? Select TWO.
- Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures.
- Pin releases to reviewed immutable image digests and record image plus model artifact versions.
- Choose a GPU configuration with sufficient memory or validated model compression while benchmarking cost per query.
- Restrict invoke access to the necessary principal and endpoint, using appropriate short-lived authentication.
- Inspect model weights, KV or activation memory, concurrency load, GPU memory, and supported device types.
Explanation
Correct Answers
C:Choose a GPU configuration with sufficient memory or validated model compression while benchmarking cost per query. This is the targeted corrective response for gpu cost and memory fit for large embedding model. CPU cores do not expand device memory; accelerator selection must match model footprint and request shape. Verify the diagnosis using: Inspect model weights, KV or activation memory, concurrency load, GPU memory, and supported device types. Confirm success using: The model loads at target concurrency without OOM and meets latency and cost targets. This matters here because a text embedding model cannot fit into a chosen tiny GPU's memory, but a team only considers increasing container….
E:Inspect model weights, KV or activation memory, concurrency load, GPU memory, and supported device types. This inspects evidence relevant to gpu cost and memory fit for large embedding model. CPU cores do not expand device memory; accelerator selection must match model footprint and request shape. After identifying the cause, the matching correction is: Choose a GPU configuration with sufficient memory or validated model compression while benchmarking cost per query. This matters here because a text embedding model cannot fit into a chosen tiny GPU's memory, but a team only considers increasing container….
Incorrect Answers
A:Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures. This is an action or diagnostic relevant to feature online entity key mismatch, not one of the required two steps. In this scenario verify: Inspect model weights, KV or activation memory, concurrency load, GPU memory, and supported device types. Then correct: Choose a GPU configuration with sufficient memory or validated model compression while benchmarking cost per query.
B:Pin releases to reviewed immutable image digests and record image plus model artifact versions. This is an action or diagnostic relevant to model artifact image digest reproducibility, not one of the required two steps. In this scenario verify: Inspect model weights, KV or activation memory, concurrency load, GPU memory, and supported device types. Then correct: Choose a GPU configuration with sufficient memory or validated model compression while benchmarking cost per query. This matters here because a text embedding model cannot fit into a chosen tiny GPU's memory, but a team only considers increasing container….
D:Restrict invoke access to the necessary principal and endpoint, using appropriate short-lived authentication. This is an action or diagnostic relevant to public endpoint iam oversharing, not one of the required two steps. In this scenario verify: Inspect model weights, KV or activation memory, concurrency load, GPU memory, and supported device types. Then correct: Choose a GPU configuration with sufficient memory or validated model compression while benchmarking cost per query. This matters here because a text embedding model cannot fit into a chosen tiny GPU's memory, but a team only considers increasing container….
Question 690
During a staged restoration test at a secondary serving deployment, the following condition occurs: A document classification service sends huge media files through synchronous prediction calls whose processing exceeds clients' timeout limits. The team must prove an actual user-visible improvement without weakening access controls. Which targeted engineering change most directly addresses the failure?
- Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests.
- Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.
- Configure the supported private DNS, network route and endpoint access path without granting public ingress.
- Roll out a small canary percentage first, monitor error and quality guardrails and expand only after acceptance.
Explanation
Correct Answer
A:Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests. This is the targeted corrective response for online prediction timeout and batch fallback. Synchronous request limits cannot be solved merely by expanding the model context or retrying indefinitely. Verify the diagnosis using: Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion. Confirm success using: Large documents finish without client timeout and consumers retrieve signed results using recorded job IDs. This matters here because during a staged restoration test at a secondary serving deployment, the following condition occurs: A document….
Incorrect Answers
B:Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests. This action addresses inference preprocessing tokenization mismatch, not the failure in the described online prediction timeout and batch fallback case. The targeted correction is: Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests.
C:Configure the supported private DNS, network route and endpoint access path without granting public ingress. This action addresses private vpc routing failure for serving, not the failure in the described online prediction timeout and batch fallback case. The targeted correction is: Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests.
D:Roll out a small canary percentage first, monitor error and quality guardrails and expand only after acceptance. This action addresses canary gradual traffic rollout, not the failure in the described online prediction timeout and batch fallback case. The targeted correction is: Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests.