Java SE 17 (1Z0-829)

It tests practical Java SE 17 language skill across five objective areas: date/time, text, numeric and boolean handling; collections and streams; program flow control; exceptions and local variable type inference; and object-oriented concepts with functional interfaces. Expect code-reading questions where you must trace output or spot a compile error, not trivia recall.

We cannot state these figures reliably. The official Oracle University page for this exam was returning a maintenance notice when we checked, so item count, time limit, passing score and fee are all unconfirmed here. Verify current logistics directly with Oracle or your test provider before you schedule.

Candidates generally find it demanding because the objectives assume working fluency, not memorization. Questions often hinge on small details: overload resolution, autoboxing, stream laziness, exception ordering in multi-catch, or why var is illegal in a particular declaration. If you only read about these topics you will likely misjudge the tricky options.

Start with the areas that underpin everything else: object-oriented concepts, functional interfaces and lambdas, then collections and streams. Date/time and numeric/text handling are largely API familiarity and reward short daily practice. Leave exceptions and var until last only if you are already comfortable reading stack traces and compiler messages.

Three patterns recur: assuming a stream operation runs eagerly when it is lazy; forgetting that checked exceptions must be handled or declared, including inside lambdas; and misjudging what var infers or where it is forbidden. Another frequent slip is confusing compile-time errors with runtime exceptions when tracing a snippet.

Retake rules, waiting periods and costs are set by Oracle and were not available from the source we could access, so treat any figure you hear as unverified until you confirm it with Oracle. In practice, plan to pass first time: book only when practice scores are consistently comfortable, and keep your weak objective list for a focused second attempt.

That depends heavily on existing experience. A developer already writing Java 17 daily may need a few weeks of focused objective-by-objective practice; someone coming from an older Java version should budget longer for records, sealed types, switch expressions and text blocks. Track progress by objective rather than by hours.

Hands-on coding is necessary. Many exam traps only become obvious when you compile the code yourself and read the actual error message. Write small programs for each objective, intentionally introduce mistakes, and predict the output before running. That habit transfers directly to code-tracing questions.

No. This is independent study material written for candidates preparing for the Java SE 17 Developer exam. It is not produced, reviewed or endorsed by Oracle, and it does not reproduce any official question bank. Always treat Oracle's own exam objectives and logistics pages as the authoritative source.