Quick Answer
The answer is the `initCause(Throwable)` method. This is the correct choice because the `Throwable` class provides `initCause` specifically to set an exception’s cause after the exception object has already been constructed, which is essential when using a no-arg constructor that does not accept a cause parameter. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept often appears in exception chaining questions where a custom exception is created first and the underlying cause is determined later; a common trap is assuming the cause can be set multiple times, but `initCause` can only be called once—a second invocation throws an `IllegalStateException`. To remember this, think of “init” as “initialize once”: you can only set the cause at the beginning of the exception’s life, not rewire it later.
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.
Given an exception chain where a custom exception is created with a cause, which method is used to set the cause after construction?
The cause can only be set via constructor.
Why wrong: initCause can be used after construction.
setCause(Throwable)
Why wrong: No such method in Throwable.
addSuppressed(Throwable)
Why wrong: Used for suppressed exceptions, not cause.
initCause(Throwable)
Allows setting the cause after construction.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
initCause(Throwable)
Option D is correct because `initCause(Throwable)` is the method provided by the `Throwable` class to set the cause of an exception after the exception has been constructed. This is useful when the exception must be created without a cause (e.g., via a no-arg constructor) and the cause is determined later. The cause can only be set once; a second call will throw an `IllegalStateException`.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
The cause can only be set via constructor.
Why it's wrong here
initCause can be used after construction.
setCause(Throwable)
Why it's wrong here
No such method in Throwable.
addSuppressed(Throwable)
Why it's wrong here
Used for suppressed exceptions, not cause.
initCause(Throwable)
Why this is correct
Allows setting the cause after construction.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates confuse `initCause(Throwable)` with `addSuppressed(Throwable)`, or assume the cause can only be set via constructor, missing the post-construction capability that `initCause` provides.
Detailed technical explanation
Under the hood, `initCause(Throwable)` stores the cause in a private field `cause` within the `Throwable` object, which is then accessible via `getCause()`. This method enforces a one-time initialization: if the cause was already set via constructor or a prior `initCause` call, an `IllegalStateException` is thrown. In real-world scenarios, this is critical when wrapping exceptions in custom exception classes that need to defer cause assignment until additional context is available, such as in layered frameworks where the root exception is propagated.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Handling Exceptions — study guide chapter
Learn the concepts, then practise the questions
Handling Exceptions practice questions
Targeted practice on this topic area only
All 1Z0-829 questions
509 questions across all exam domains
Oracle Certified Professional Java SE 17 Developer 1Z0-829 study guide
Full concept coverage aligned to exam objectives
1Z0-829 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise 1Z0-829 questions linked to Handling Date, Time, Text, Numeric and Boolean Values.
Practise 1Z0-829 questions linked to Controlling Program Flow.
Practise 1Z0-829 questions linked to Utilizing Java Object-Oriented Approach.
Practise 1Z0-829 questions linked to Handling Exceptions.
Practise 1Z0-829 questions linked to Working with Arrays and Collections.
Practise 1Z0-829 questions linked to Working with Streams and Lambda Expressions.
Practise 1Z0-829 questions linked to Java Platform Overview and Packaging.
Practise 1Z0-829 questions linked to Java I/O API and Securing Applications.
Practise 1Z0-829 questions linked to 1Z0-829 fundamentals.
Practise 1Z0-829 questions linked to 1Z0-829 scenario.
Practise 1Z0-829 questions linked to 1Z0-829 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Handling Exceptions — This question tests Handling Exceptions — Read the scenario before looking for a memorised answer..
The correct answer is: initCause(Throwable) — Option D is correct because `initCause(Throwable)` is the method provided by the `Throwable` class to set the cause of an exception after the exception has been constructed. This is useful when the exception must be created without a cause (e.g., via a no-arg constructor) and the cause is determined later. The cause can only be set once; a second call will throw an `IllegalStateException`.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 25, 2026
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.