fix(question-bank): correct six user-reported CLF-C02 question defects - #225
Open
nastaso wants to merge 1 commit into
Open
fix(question-bank): correct six user-reported CLF-C02 question defects#225nastaso wants to merge 1 commit into
nastaso wants to merge 1 commit into
Conversation
Closes #216, #214, #213, #212, #207, #206. Each report was verified against AWS documentation before any edit, and cross-checked with a second model. Two reports were wrong about the answer key and are answered in the issue rather than by changing a correct question. q478 (#207): marked answer flipped D -> B. "Resizable compute capacity in the cloud" is AWS's description of Amazon EC2, not Lambda. AWS documents that you can "call it directly from any web or mobile app", so the old key (D) marked a genuine documented benefit as the non-benefit. Explanation rewritten; the old one asserted the opposite of the AWS docs. q889 (#212): explanation's distractor paragraph discussed Macie and Shield, which are not options in this question. Rewritten to cover the real options (Secrets Manager, Systems Manager, Certificate Manager). Answer unchanged. q387 (#214): reporter's claim that CloudTrail should be the answer is wrong (that option also deletes every IAM user with access, which AWS does not advise). Answer unchanged, but the explanation described three options that do not exist in the question, so it was rewritten against the real options. q093 (#206): option C misspelled the service as "Amazon Recognition". q583 (#216): stem did not say whose costs it meant. Reworded to ask which cost a company stops paying for directly when it moves off its own data center. q231 (#213): reporter's alternatives (Config, Artifact, Audit Manager) are not options, so the answer stands, but "ensure compliance" was genuinely loose. Stem tightened to name the mechanism without giving away the service. Ledger regenerated via npm run bank:lastmod.
Deploying cloudcertprep with
|
| Latest commit: |
767cb34
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9cf7db05.cloudcertprep.pages.dev |
| Branch Preview URL: | https://fix-question-errors-batch.cloudcertprep.pages.dev |
Owner
Author
|
CI green across all seven checks, including Second-opinion cross-check: ran every AWS-correctness call past Codex ( Not merging, per repo rules. Over to @nastaso. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Works through the seven open user-reported question-error issues as one change, since they touch the same banks and
validate-questionsgates them together.Every report was verified against AWS documentation before anything was edited, and independently cross-checked by a second model (Codex/GPT-5.6). Two reports turned out to be wrong about the answer key; those questions were not changed to match the report.
Closes #216, #214, #213, #212, #207, #206.
D->B, explanation rewrittenThe one real answer-key error: q478 (#207)
The bank marked D ("AWS Lambda can be called directly from any mobile app") as the non-benefit. That is wrong on both halves:
The previous explanation asserted the opposite of the AWS docs ("Lambda functions cannot be invoked directly from a mobile app"), so it has been rewritten too.
Source: AWS Well-Architected, Lambda concept (the source the reporter cited) and aws.amazon.com/ec2.
Two explanations described options that do not exist
q889 (#212) and q387 (#214) both had distractor paragraphs written against a different option set: q889 discussed Macie and Shield, q387 discussed "closing the account" and "opening a new root account". Neither appears in its question. Both rewritten against the real options. Neither answer key changed.
q387's reporter argued CloudTrail should be the answer. It should not: that option also deletes every IAM user with access to your resources, and AWS guidance is to deactivate the IAM users you did not create, not all of them. The rewritten explanation now says this explicitly, so the next reader gets the reasoning.
#204 (q280) is not a content bug
The reporter selected the correct answers and was still graded incorrect. The question content is right (NACLs + security groups). The cause is in the review UI:
QuestionReviewCard.tsx:96-98paints every correct option green whether or not the user selected it, and there is no "you picked this" state. An unanswered or half-answered multi-answer question therefore renders identically to a fully correct one while still being badged INCORRECT.That is a real user-facing bug, but it is a UI/design change needing screenshot verification, so it is deliberately not bundled into a question-bank PR. #204 should stay open and be re-scoped. Details in the handoff.
How was this tested?
npm run validate- all questions valid, warning count unchanged from baseline (19, all pre-existingsaa-c03ones)npm run check-astro check0 errors, eslint clean, 300 tests / 26 suites passednpm run bank:lastmod- freshness ledger regenerated (unit-test gated bybankFreshness.test.ts)Checklist
npm run validatepasses locallynpm run checkpasses locallyNote on #205
PR #205 (q808 answer count) is correct and was deliberately not absorbed here, so the external contributor keeps authorship. It touches
src/data/clf-c02/domain2.jsonandbank-lastmod.json, so whichever of the two merges second needs anpm run bank:lastmodre-run to settle the ledger hash. No semantic conflict: different questions.Screenshots (UI changes only)
Not applicable, content-only change.