The answer is that providing a constructor accepting both a String message and a Throwable cause is a correct best practice for custom exception constructors. This is because Java’s exception chaining mechanism relies on the super(message, cause) call, which stores the underlying cause internally and makes it retrievable via getCause(), enabling precise error reporting and debugging. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of exception design patterns and the Throwable class hierarchy; a common trap is assuming a single-argument constructor is sufficient for chaining, when in fact the two-argument constructor is the standard for preserving both the human-readable description and the root cause. A useful memory tip is to remember the acronym “MC” for Message and Cause—always include both in your custom exception constructors to ensure full traceability.
1Z0-829 Handling Exceptions Practice Question
This 1Z0-829 practice question tests your understanding of handling exceptions. 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 TWO statements about creating custom exceptions are correct? (Choose two.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
It is good practice to provide a constructor that takes a String message and a Throwable cause.
Option D is correct because it is a well-established best practice in Java to provide a constructor that accepts both a String message and a Throwable cause, enabling precise error reporting and chaining of exceptions. This allows developers to pass a human-readable description along with the underlying cause, which is essential for debugging and logging.
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.
✗
Custom exceptions should extend Error to indicate fatal errors.
Why it's wrong here
Error is not for application exceptions.
✗
Custom exception classes should be declared final to prevent subclassing.
Why it's wrong here
Not required or recommended.
✗
Custom exceptions must implement the Exception interface.
Why it's wrong here
Exception is a class, not interface.
✓
It is good practice to provide a constructor that takes a String message and a Throwable cause.
Why this is correct
Common to have such constructor.
Related concept
Read the scenario before looking for a memorised answer.
✓
When calling super(cause) in a custom exception constructor, the cause is automatically set.
Why this is correct
Throwable constructor does that.
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 to extend Throwable (or a subclass) with implementing a nonexistent Exception interface, or they mistakenly think that custom exceptions must be declared final to prevent misuse, when in fact Java allows and encourages subclassing of custom exceptions for more granular error handling.
Detailed technical explanation
How to think about this question
Under the hood, when a custom exception constructor calls super(cause), it invokes the Throwable constructor that initializes the cause field, which is then accessible via getCause(). This mechanism is part of the chained exception facility introduced in Java 1.4, allowing developers to wrap lower-level exceptions (e.g., SQLException) into higher-level application exceptions without losing the original stack trace. In real-world scenarios, such as in a Spring Boot service layer, this pattern is crucial for preserving the root cause of a failure when translating checked exceptions to runtime exceptions.
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 practitioner preparing for the 1Z0-829 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
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.
Handling Exceptions — This question tests Handling Exceptions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: It is good practice to provide a constructor that takes a String message and a Throwable cause. — Option D is correct because it is a well-established best practice in Java to provide a constructor that accepts both a String message and a Throwable cause, enabling precise error reporting and chaining of exceptions. This allows developers to pass a human-readable description along with the underlying cause, which is essential for debugging and logging.
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 →
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.