Original course questions with explained answers. This assessment is for learning; it does not predict certification exam results.
Free sample questions with explanations
Try these sample questions without an account. Choose your answer, then open the explanation. Sign in below to take the full scored test and save your result.
1. Which input reveals the supplied comparison bug?
- 10
- 9 only
- Any screenshot
Show answer and explanation for question 1
Correct answer: A. 10
The equality boundary distinguishes < from <=.
2. What should you do when an acceptance test reveals a defect?
- Delete the test
- Correct the implementation or clarify the requirement
- Trust confident prose
Show answer and explanation for question 2
Correct answer: B. Correct the implementation or clarify the requirement
Tests express the requirement; defects should be addressed.
3. What belongs in a safe coding request?
- Production secrets
- Unbounded system access
- Input/output contract and permitted actions
Show answer and explanation for question 3
Correct answer: C. Input/output contract and permitted actions
A bounded specification makes review and testing possible.
4. A low-severity ticket is exactly at its target age. Under the written rule, which label is expected?
- URGENT_CANDIDATE, because age >= target independently satisfies the OR rule.
- ROUTINE_CANDIDATE, because only high severity can qualify.
- REJECTED, because equality is invalid.
Show answer and explanation for question 4
Correct answer: A. URGENT_CANDIDATE, because age >= target independently satisfies the OR rule.
The specification contains an OR condition and an inclusive age boundary. A dramatic high-severity overdue example cannot independently test either of those distinctions.
5. Generated code and generated tests both say T002 is routine, but the approved matrix says urgent. What has the green suite proved?
- The approved specification is wrong.
- The two generated artifacts agree; independent requirement verification is still missing.
- The script is ready to update real tickets.
Show answer and explanation for question 5
Correct answer: B. The two generated artifacts agree; independent requirement verification is still missing.
Shared assumptions can make implementation and tests agree on the same mistake. Recover expected values from the approved specification and manual trace, then review both code and assertion changes.
Sign in to take this free practice test and save your result.
Sign in