The correct answer is that a switch expression must be exhaustive, meaning all possible input values must be covered by a case or a default branch. This is a fundamental requirement of the switch expression in Java 17 because, unlike the traditional switch statement, a switch expression produces a value and must guarantee a result for every possible input. The arrow syntax (->) used in switch expressions automatically terminates each branch, preventing the fall-through behavior of the classic switch, but it does not remove the need for exhaustiveness. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept often appears in questions about the differences between switch statements and expressions, with a common trap being that candidates confuse the automatic break of arrow syntax with the ability to omit a default case. Remember: if your switch expression uses arrow syntax, you still must cover all cases—think of it as "every arrow needs a target." A useful memory tip is "Exhaustive Expression: Every value gets a path."
1Z0-829 Controlling Program Flow Practice Question
This 1Z0-829 practice question tests your understanding of controlling program flow. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which three of the following statements about the switch expression in Java 17 are correct?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A switch expression with arrow syntax does not require break.
Option A is correct because in a switch expression with arrow syntax (->), each branch is a single expression or block that is automatically terminated, eliminating the need for a break statement. The arrow syntax implicitly prevents fall-through, making the code more concise and less error-prone.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
A switch expression with arrow syntax does not require break.
Why this is correct
Arrow syntax implicitly prevents fall-through, so break is unnecessary.
Related concept
Read the scenario before looking for a memorised answer.
✓
A switch expression with colon syntax can use yield to return a value.
Why this is correct
In colon syntax, yield is used to provide a value for the expression.
Related concept
Read the scenario before looking for a memorised answer.
✗
A switch expression cannot be used with an enum type.
Why it's wrong here
Switch expressions can be used with enum types.
✗
A switch expression must include a default branch even if all cases are covered.
Why it's wrong here
If all cases are covered exhaustively, a default branch is optional.
✓
A switch expression must be exhaustive.
Why this is correct
Switch expressions must cover all possible values or have a default branch.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the requirement for a default branch in switch expressions with the behavior of switch statements, mistakenly thinking a default is always mandatory even when all cases are covered.
Detailed technical explanation
How to think about this question
Under the hood, the Java compiler treats switch expressions as poly expressions that must produce a value for every possible input, enforcing exhaustiveness at compile time. For enum types, the compiler can verify that all enum constants are covered, and if not, it requires a default branch to handle any future additions. A real-world scenario is using switch expressions with sealed classes or records, where the compiler can statically check that all permitted subtypes are handled, ensuring type-safe pattern matching.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Controlling Program Flow — This question tests Controlling Program Flow — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: A switch expression with arrow syntax does not require break. — Option A is correct because in a switch expression with arrow syntax (->), each branch is a single expression or block that is automatically terminated, eliminating the need for a break statement. The arrow syntax implicitly prevents fall-through, making the code more concise and less error-prone.
What should I do if I get this 1Z0-829 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which statement is correct about the following switch expression? String result = switch(day) { case MONDAY, TUESDAY -> "weekday"; case WEDNESDAY -> "midweek"; default -> "other"; };
medium
A.The switch expression is not allowed with a colon.
✓ B.The switch expression must be terminated with a semicolon.
C.The default branch is optional.
D.The arrow operator requires a yield statement.
Why B: Option B is correct because switch expressions in Java must be terminated with a semicolon, as they produce a value that is assigned to a variable. The given code uses the arrow syntax (->) and assigns the result to a String variable, so a semicolon is required at the end of the entire switch expression.
Last reviewed: Jun 25, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 1Z0-829 practice question is part of Courseiva's free Oracle certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 1Z0-829 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.