Exam Bundle

A representative image set demonstrates whether the managed API meets accuracy and supported-feature requirements within cost bounds. This would verify a different operation: Compare Amazon Rekognition's supported capabilities against the need for custom features before committing to training. That separate action addresses: An image-processing system needs managed detection of standard objects and text in product photos, but a project proposal requires a custom vision model for each image type. It cannot establish the required Riverton Utilities correction for: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The decisive acceptance check is instead: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

A holdout run produces numeric unit forecasts and is evaluated with documented regression or forecasting error metrics. This would verify a different operation: Select an appropriate regression or time-series modeling approach aligned to the continuous demand target and its evaluation horizon. That separate action addresses: An inventory forecasting team proposes a binary classification algorithm although the desired output is a continuous quantity of product units. It cannot establish the required Riverton Utilities correction for: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The decisive acceptance check is instead: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

A realistic concurrency test meets the latency SLA and the final choice documents the measured accuracy-cost tradeoff. This would verify a different operation: Include inference latency, compute cost and model size in a feasibility benchmark against smaller compatible candidates. That separate action addresses: A fraud detection service requires millisecond decisions but a very large transformer is selected solely because its offline F1 score is highest. It cannot establish the required Riverton Utilities correction for: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The decisive acceptance check is instead: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

Choose an unsupervised anomaly-detection approach suited to the available feature data and explicitly define anomaly review outcomes. It does not directly address the Cedarfield Hospitality case: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The relevant acceptance criterion for this case is: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

Compare model and deployment options against data residency, access policy and cost constraints before deciding on Bedrock or a supported hosted alternative. It does not directly address the Cedarfield Hospitality case: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The relevant acceptance criterion for this case is: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

Use SageMaker's configured channel path or environment variables for training data and remove developer-specific bucket references. It does not directly address the Cedarfield Hospitality case: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The relevant acceptance criterion for this case is: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

A holdout run produces numeric unit forecasts and is evaluated with documented regression or forecasting error metrics. This would verify a different operation: Select an appropriate regression or time-series modeling approach aligned to the continuous demand target and its evaluation horizon. That separate action addresses: An inventory forecasting team proposes a binary classification algorithm although the desired output is a continuous quantity of product units. It cannot establish the required Cedarfield Hospitality correction for: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The decisive acceptance check is instead: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

The built-in training algorithm reads an approved small input channel and no longer reports record-deserialization errors. This would verify a different operation: Convert the training input into the supported RecordIO, CSV or other documented algorithm format and validate content type. That separate action addresses: A team deploys a SageMaker built-in algorithm with an input record format incompatible with the algorithm's required channel parser. It cannot establish the required Cedarfield Hospitality correction for: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The decisive acceptance check is instead: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

The compressed model meets the artifact-size target and its measured accuracy loss stays within the approved limit. This would verify a different operation: Evaluate supported pruning or quantization techniques with quality and compatibility checks for the intended runtime. That separate action addresses: A model developer tries to reduce a large inference artifact by removing random trained layers without validation or a deployment-size target. It cannot establish the required Cedarfield Hospitality correction for: A product classifier reports a high micro-averaged F1 but hides very poor performance on a critical rare product category. The decisive acceptance check is instead: The report shows every priority class's performance and a rare-category failure cannot be masked by majority volume.

Validate tokenizer and embedding compatibility or use the correct documented resize and artifact versioning procedure. It does not directly address the Alpine Healthcare case: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The relevant acceptance criterion for this case is: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

Evaluate an appropriate generative foundation model or managed AI capability while constraining input length, retrieval and output validation. It does not directly address the Alpine Healthcare case: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The relevant acceptance criterion for this case is: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

Evaluate supported pruning or quantization techniques with quality and compatibility checks for the intended runtime. It does not directly address the Alpine Healthcare case: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The relevant acceptance criterion for this case is: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

The selected approach meets the required recall and precision tradeoff on the untouched production-like class distribution. This would verify a different operation: Select a classifier and decision threshold based on false-negative cost and class-aware metrics rather than majority-class accuracy. That separate action addresses: A defect prediction project has very few confirmed positive labels and proposes to optimize raw accuracy on an unbalanced evaluation dataset. It cannot establish the required Alpine Healthcare correction for: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The decisive acceptance check is instead: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

The chosen checkpoint stops before sustained validation degradation and improves the untouched test-set performance. This would verify a different operation: Apply an appropriate regularization or early-stopping strategy selected against validation behavior instead of increasing epochs blindly. That separate action addresses: A production classifier's training loss steadily decreases while validation loss rises, indicating the model is memorizing the training examples. It cannot establish the required Alpine Healthcare correction for: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The decisive acceptance check is instead: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

The built-in training algorithm reads an approved small input channel and no longer reports record-deserialization errors. This would verify a different operation: Convert the training input into the supported RecordIO, CSV or other documented algorithm format and validate content type. That separate action addresses: A team deploys a SageMaker built-in algorithm with an input record format incompatible with the algorithm's required channel parser. It cannot establish the required Alpine Healthcare correction for: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The decisive acceptance check is instead: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

Configure SageMaker automatic model tuning with the declared validation objective and bounded hyperparameter search ranges. It does not directly address the Juniper Media case: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The relevant acceptance criterion for this case is: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

Evaluate an appropriate generative foundation model or managed AI capability while constraining input length, retrieval and output validation. It does not directly address the Juniper Media case: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The relevant acceptance criterion for this case is: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

Validate tokenizer and embedding compatibility or use the correct documented resize and artifact versioning procedure. It does not directly address the Juniper Media case: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The relevant acceptance criterion for this case is: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

The experiment record displays expected named metrics with values matching the training log for a controlled run. This would verify a different operation: Emit parseable training and validation metrics and configure correct SageMaker metric definitions for the container output. That separate action addresses: SageMaker managed training metrics do not appear in experiment reports because the custom container never emits the configured metric pattern. It cannot establish the required Juniper Media correction for: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The decisive acceptance check is instead: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

The adapted model gains target-domain quality without unacceptable regression on the original reference tasks. This would verify a different operation: Use a suitably small and tested fine-tuning learning rate or parameter-efficient approach with a retained baseline evaluation. That separate action addresses: A team fine-tunes a pre-trained model with a learning rate so high that its previously learned useful capabilities deteriorate rapidly. It cannot establish the required Juniper Media correction for: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The decisive acceptance check is instead: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

An approved multilingual reference set meets translation acceptance checks without running custom model infrastructure when unnecessary. This would verify a different operation: Assess Amazon Translate for the supported target language pair and compare it with any genuinely required custom terminology handling. That separate action addresses: A machine translation feature plans to retrain a multilingual sequence-to-sequence model despite requiring only a common language pair already supported by a managed AWS service. It cannot establish the required Juniper Media correction for: An ML review compares two model variants using different holdout sets and claims the one with higher score is superior. The decisive acceptance check is instead: The paired model comparison uses matching sample IDs and reproducible evaluation settings for both candidates.

Emit parseable training and validation metrics and configure correct SageMaker metric definitions for the container output. It does not directly address the Timberline Foods case: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The relevant acceptance criterion for this case is: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

Assess temporal data sufficiency, sampling frequency and known-future covariates before comparing time-series models. It does not directly address the Timberline Foods case: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The relevant acceptance criterion for this case is: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

Configure rank-aware data sharding or distributed sampling so every worker receives the intended subset for the epoch. It does not directly address the Timberline Foods case: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The relevant acceptance criterion for this case is: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

A repeated training run keeps finite gradients and loss while meeting the declared convergence criterion. This would verify a different operation: Inspect training diagnostics and apply suitable learning-rate reduction or gradient clipping with controlled numerical checks. That separate action addresses: A custom model has an unstable optimizer and loss becomes nonfinite after a few updates due to excessive gradient magnitudes. It cannot establish the required Timberline Foods correction for: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The decisive acceptance check is instead: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

The selection report compares test metrics, training cost and operational complexity on a common fixed dataset. This would verify a different operation: Benchmark suitable tabular algorithms such as SageMaker XGBoost against the complex model using the same split and budget. That separate action addresses: An analyst trains a high-capacity neural network on a small, mostly numeric transaction table without first benchmarking simpler tabular methods. It cannot establish the required Timberline Foods correction for: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The decisive acceptance check is instead: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

A holdout run produces numeric unit forecasts and is evaluated with documented regression or forecasting error metrics. This would verify a different operation: Select an appropriate regression or time-series modeling approach aligned to the continuous demand target and its evaluation horizon. That separate action addresses: An inventory forecasting team proposes a binary classification algorithm although the desired output is a continuous quantity of product units. It cannot establish the required Timberline Foods correction for: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The decisive acceptance check is instead: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

Enable appropriate SageMaker managed Spot training checkpoints in durable storage and a tested resume workflow. It does not directly address the Keystone BioLabs case: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The relevant acceptance criterion for this case is: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

Configure rank-aware data sharding or distributed sampling so every worker receives the intended subset for the epoch. It does not directly address the Keystone BioLabs case: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The relevant acceptance criterion for this case is: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

Select an appropriate regression or time-series modeling approach aligned to the continuous demand target and its evaluation horizon. It does not directly address the Keystone BioLabs case: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The relevant acceptance criterion for this case is: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

The chosen checkpoint stops before sustained validation degradation and improves the untouched test-set performance. This would verify a different operation: Apply an appropriate regularization or early-stopping strategy selected against validation behavior instead of increasing epochs blindly. That separate action addresses: A production classifier's training loss steadily decreases while validation loss rises, indicating the model is memorizing the training examples. It cannot establish the required Keystone BioLabs correction for: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The decisive acceptance check is instead: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

The feasibility report identifies supported series and validates forecasts without silently fabricating missing chronological observations. This would verify a different operation: Assess temporal data sufficiency, sampling frequency and known-future covariates before comparing time-series models. That separate action addresses: An ML engineer chooses a built-in forecasting method without confirming that multiple product series contain sufficient and regularly spaced history. It cannot establish the required Keystone BioLabs correction for: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The decisive acceptance check is instead: The experiment record shows no selection decisions based on final test labels before the locked evaluation.

An interruption test restarts from the last saved checkpoint rather than the initial epoch and preserves model state. This would verify a different operation: Enable appropriate SageMaker managed Spot training checkpoints in durable storage and a tested resume workflow. That separate action addresses: A lengthy training job uses Spot Instances without checkpoints and loses all progress when a capacity interruption stops the instance. It cannot establish the required Keystone BioLabs correction for: A model validation workflow repeatedly tunes its hyperparameters on the same final test set, inflating the reported out-of-sample quality. The decisive acceptance check is instead: The experiment record shows no selection decisions based on final test labels before the locked evaluation.