This is the suite's regression gate. Answer every question, then run the suite. Wrong answers show an explanation — read it, then re-run. In this course, like on a real team, you don't merge on a red build.
01.Which command verifies your JDK installation worked?
java -version in a fresh PowerShell. Any 21.x output means the JDK is installed and on your PATH.
02.You installed the JDK, but PowerShell says “'java' is not recognized”. Most likely fix?
The #1 gotcha: an open shell keeps its old PATH. Close and reopen it; if it still fails, set JAVA_HOME and add %JAVA_HOME%\bin to Path.
03.Why keep your project out of OneDrive-synced folders like Desktop or Documents?
Cloud sync grabs file locks mid-build and causes maddening intermittent failures. C:\dev\ is your friend.
04.Which Git command records a labeled snapshot into permanent history?
add stages, commit snapshots (with your message), push uploads. Write commit messages like defect summaries — a skill you already have.
05.In mvn test output, an Error (vs a Failure) means…
Failure = assertion mismatch (point at the app). Error = the test's own code blew up, like NoSuchElementException (point at the test). That distinction is a daily skill.
06.The suite fails. Where do you look first in the terminal output?
BUILD SUCCESS/FAILURE is the verdict; the first red block names the test, the expectation, and what actually happened.
passing marks this suite test complete on the roadmap · revision aid: the suite cheatsheet