Question 510
At Cedarfield Hospitality, the infrastructure services team maintains hotel booking and shared Linux services under requirements for guest-data privacy and reliable remote access. The acceptance reviewer must validate: A release repository includes private API keys because developers assume adding the files to .gitignore later removes them from Git history. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
A new clone contains no usable secret in the tested scope and the rotated credential no longer authenticates. This measurable outcome verifies correction of: A release repository includes private API keys because developers assume adding the files to .gitignore later removes them from Git history. The associated technical action is: Remove exposed secrets from active content, rotate them and apply an approved Git history remediation while adding safe ignore rules. The Cedarfield Hospitality review checks actual behavior rather than an untested change claim.
Incorrect Answers
Only explicitly matching test account names are selected and a confusing partial-match account is excluded. This evidence pertains to an unrelated remediation: Anchor the intended regex and validate the full account identifier before applying any change, using a dry-run preview. The alternative issue is: A Bash automation uses a broad regular expression that matches unintended account names and acts on production users outside its allowlist. The current Cedarfield Hospitality problem is: A release repository includes private API keys because developers assume adding the files to .gitignore later removes them from Git history. The decisive expected evidence is instead: A new clone contains no usable secret in the tested scope and the rotated credential no longer authenticates.
Two independent test calls produce isolated results and modifications to one result do not change the other. This evidence pertains to an unrelated remediation: Use a None default and allocate the mutable dictionary inside each function invocation when independent state is required. The alternative issue is: A Python automation stores a mutable dictionary as a shared default argument and unexpectedly carries state between separate invocations. The current Cedarfield Hospitality problem is: A release repository includes private API keys because developers assume adding the files to .gitignore later removes them from Git history. The decisive expected evidence is instead: A new clone contains no usable secret in the tested scope and the rotated credential no longer authenticates.
Each asserted incident event is traceable to a retained source record and an invented event is removed during review. This evidence pertains to an unrelated remediation: Correlate the generated summary with source logs, timestamps and approved monitoring evidence before publishing the report. The alternative issue is: An organization accepts AI-generated incident reports as authoritative without checking the claimed system events against actual telemetry. The current Cedarfield Hospitality problem is: A release repository includes private API keys because developers assume adding the files to .gitignore later removes them from Git history. The decisive expected evidence is instead: A new clone contains no usable secret in the tested scope and the rotated credential no longer authenticates.