Question 490
At Redstone Aviation, the systems reliability team maintains maintenance scheduling Linux workloads under requirements for tested recovery and restrictive network access. Following a proposed correction, the team checks: A Python configuration loader assumes every YAML-like value is a string and fails when a numeric resource limit is provided. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
Valid integer input is accepted and malformed input produces a controlled validation error without writing configuration. This measurable outcome verifies correction of: A Python configuration loader assumes every YAML-like value is a string and fails when a numeric resource limit is provided. The associated technical action is: Validate expected Python data types and convert numeric input explicitly with appropriate error handling. The Redstone Aviation review checks actual behavior rather than an untested change claim.
Incorrect Answers
The review output contains the required incident facts without exposing protected identities or secrets to an unauthorized service. This evidence pertains to an unrelated remediation: Use the approved private or local analysis workflow and redact sensitive log fields according to the organization's data-governance policy. The alternative issue is: A support engineer sends complete production authentication logs containing personal identifiers to an unapproved public AI service for summarization. The current Redstone Aviation problem is: A Python configuration loader assumes every YAML-like value is a string and fails when a numeric resource limit is provided. The decisive expected evidence is instead: Valid integer input is accepted and malformed input produces a controlled validation error without writing configuration.
The revised plan contains only required permissions and a test unauthorized operation is denied after deployment. This evidence pertains to an unrelated remediation: Perform a security policy review and plan or diff validation on generated infrastructure changes before an authorized merge. The alternative issue is: A team asks an AI tool to write deployment IaC but merges a broad production IAM permission grant without checking least-privilege boundaries. The current Redstone Aviation problem is: A Python configuration loader assumes every YAML-like value is a string and fails when a numeric resource limit is provided. The decisive expected evidence is instead: Valid integer input is accepted and malformed input produces a controlled validation error without writing configuration.
A maliciously shaped test pathname is handled safely and the reviewed script passes lint and functional tests. This evidence pertains to an unrelated remediation: Require human code review, shell linting and a sandboxed test with adversarial input before accepting generated automation. The alternative issue is: An AI assistant proposes shell code with an unquoted variable that could delete unintended directories, and the operator relies on the generated explanation alone. The current Redstone Aviation problem is: A Python configuration loader assumes every YAML-like value is a string and fails when a numeric resource limit is provided. The decisive expected evidence is instead: Valid integer input is accepted and malformed input produces a controlled validation error without writing configuration.