Question 400
At Granite SaaS, the production MLOps team maintains multi-tenant inference and model release pipelines under requirements for least-privilege deployment and measurable service quality. Following the controlled change, the team validates: A computer-vision model fails on slightly rotated images even though real deployment images naturally vary in orientation within valid limits. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
The robustness benchmark improves on legitimate rotated examples while clean-image accuracy remains above its acceptance floor. This is observable proof for correction of: A computer-vision model fails on slightly rotated images even though real deployment images naturally vary in orientation within valid limits. The approved design change is: Introduce validated label-preserving augmentation on training data and retain the unchanged holdout image set. The Granite SaaS acceptance test separates measured ML behavior from an unverified implementation claim.
Incorrect Answers
The test matrix isolates the marginal impact of the feature and optimizer changes without conflating their effects. This would verify a different operation: Run controlled ablations or reproducible one-factor comparisons while holding other settings fixed. That separate action addresses: A model accuracy experiment introduces a new feature and several new hyperparameters at once, preventing attribution of the observed gain. It cannot establish the required Granite SaaS correction for: A computer-vision model fails on slightly rotated images even though real deployment images naturally vary in orientation within valid limits. The decisive acceptance check is instead: The robustness benchmark improves on legitimate rotated examples while clean-image accuracy remains above its acceptance floor.
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 Granite SaaS correction for: A computer-vision model fails on slightly rotated images even though real deployment images naturally vary in orientation within valid limits. The decisive acceptance check is instead: The robustness benchmark improves on legitimate rotated examples while clean-image accuracy remains above its acceptance floor.
An auditor can reproduce the compared configurations and identify the changed input or parameter causing the metric difference. This would verify a different operation: Track training jobs, hyperparameters, dataset manifests and metrics in a reproducible SageMaker experiment catalog. That separate action addresses: A model's validation score degrades between two SageMaker runs but the experiment records lack parameter and dataset lineage. It cannot establish the required Granite SaaS correction for: A computer-vision model fails on slightly rotated images even though real deployment images naturally vary in orientation within valid limits. The decisive acceptance check is instead: The robustness benchmark improves on legitimate rotated examples while clean-image accuracy remains above its acceptance floor.