- A
Remove the `catch (Exception e)` block and rely solely on the finally block to commit or roll back based on a boolean flag set in the try block.
Why wrong: Removing the catch block and using a boolean flag in the finally block does not log exceptions or allow specific handling. If an exception occurs before the flag is set to true, the finally block will rollback, but the exception goes unlogged, making debugging difficult. This approach lacks proper exception logging and specific catch blocks.
- B
Add a separate catch block for `RuntimeException` before the existing `catch (Exception e)` and call rollback there, then rethrow the exception.
Why wrong: Adding a separate `catch (RuntimeException e)` block before the generic `catch (Exception e)` allows catching runtime exceptions, but the finally block still commits the transaction regardless of whether an exception occurred. Unless rollback is called inside the catch block, the transaction will commit, leading to inconsistent state. Also, this approach does not handle checked exceptions properly.
- C
Inside the try block, set a boolean success flag to true upon completion; in the finally block, check the flag: if false, rollback; if true, commit. Additionally, catch specific exceptions, log them, and ensure rollback logic is invoked.
Using a boolean success flag in the finally block ensures that the transaction is committed only on success and rolled back on failure. Catching specific exceptions (including RuntimeException) allows logging and immediate rollback. This provides clear, robust exception handling and maintains correct transactional integrity.
- D
Declare the method with `throws Exception` and let the caller handle the transaction rollback.
Why wrong: Declaring the method with `throws Exception` does not handle exceptions within the method; it pushes the responsibility to the caller without ensuring rollback. The caller may not roll back the transaction, leading to inconsistent state. This fails to meet the requirement of local rollback.
Implementing Transaction Rollback with Finally Block
This 1Z0-811 practice question tests your understanding of exception handling and development tools. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
You are maintaining a multi-threaded banking application that processes transactions. In the `processTransaction` method, you have a try-catch block that catches `Exception` to handle any unexpected errors. Recently, the application intermittently fails to update account balances correctly due to unhandled exceptions. The logs show that sometimes a `RuntimeException` is thrown from a nested method, but it is not being logged or handled properly, leading to inconsistent state. The team wants to improve the exception handling to ensure that all exceptions are caught, logged, and the transaction is rolled back properly. The method currently uses a primitive try-catch-finally where the finally block commits the transaction if no exception occurred. Which approach best addresses the issue while maintaining clarity and correctness?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Inside the try block, set a boolean success flag to true upon completion; in the finally block, check the flag: if false, rollback; if true, commit. Additionally, catch specific exceptions, log them, and ensure rollback logic is invoked.
Option C is correct: Use a boolean flag inside the try block to indicate success; in the finally block, check the flag to decide whether to commit or rollback. This ensures that the transaction is only committed if no exception occurred. Additionally, catching specific exceptions (including RuntimeException) and logging them ensures proper handling. Option A is wrong because using a finally block to commit always commits even if an exception occurred, unless a flag is used. Option B is wrong because adding a separate RuntimeException catch before the generic Exception catch is syntactically possible but still commits in finally unless rollback is called. Option D is wrong because using throws pushes the problem to the caller without resolving the rollback requirement.
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.
- ✗
Remove the `catch (Exception e)` block and rely solely on the finally block to commit or roll back based on a boolean flag set in the try block.
Why it's wrong here
Removing the catch block and using a boolean flag in the finally block does not log exceptions or allow specific handling. If an exception occurs before the flag is set to true, the finally block will rollback, but the exception goes unlogged, making debugging difficult. This approach lacks proper exception logging and specific catch blocks.
- ✗
Add a separate catch block for `RuntimeException` before the existing `catch (Exception e)` and call rollback there, then rethrow the exception.
Why it's wrong here
Adding a separate `catch (RuntimeException e)` block before the generic `catch (Exception e)` allows catching runtime exceptions, but the finally block still commits the transaction regardless of whether an exception occurred. Unless rollback is called inside the catch block, the transaction will commit, leading to inconsistent state. Also, this approach does not handle checked exceptions properly.
- ✓
Inside the try block, set a boolean success flag to true upon completion; in the finally block, check the flag: if false, rollback; if true, commit. Additionally, catch specific exceptions, log them, and ensure rollback logic is invoked.
Why this is correct
Using a boolean success flag in the finally block ensures that the transaction is committed only on success and rolled back on failure. Catching specific exceptions (including RuntimeException) allows logging and immediate rollback. This provides clear, robust exception handling and maintains correct transactional integrity.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Declare the method with `throws Exception` and let the caller handle the transaction rollback.
Why it's wrong here
Declaring the method with `throws Exception` does not handle exceptions within the method; it pushes the responsibility to the caller without ensuring rollback. The caller may not roll back the transaction, leading to inconsistent state. This fails to meet the requirement of local rollback.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
- Use explanations to understand the rule behind the answer.
TExam Day Tips
- Underline the problem statement mentally.
- 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-811 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.
Visual reference
What to study next
Got this wrong? Here's your next step.
Identify which 1Z0-811 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
- →
Exception Handling and Development Tools — study guide chapter
Learn the concepts, then practise the questions
- →
Exception Handling and Development Tools practice questions
Targeted practice on this topic area only
- →
All 1Z0-811 questions
509 questions across all exam domains
- →
Oracle Java Foundations 1Z0-811 study guide
Full concept coverage aligned to exam objectives
- →
1Z0-811 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related 1Z0-811 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
What is Java practice questions
Practise 1Z0-811 questions linked to What is Java.
Java Basics and Syntax practice questions
Practise 1Z0-811 questions linked to Java Basics and Syntax.
Primitives, Strings and Operators practice questions
Practise 1Z0-811 questions linked to Primitives, Strings and Operators.
Control Flow and Loops practice questions
Practise 1Z0-811 questions linked to Control Flow and Loops.
Arrays and Methods practice questions
Practise 1Z0-811 questions linked to Arrays and Methods.
Object-Oriented Programming practice questions
Practise 1Z0-811 questions linked to Object-Oriented Programming.
Exception Handling and Development Tools practice questions
Practise 1Z0-811 questions linked to Exception Handling and Development Tools.
1Z0-811 fundamentals practice questions
Practise 1Z0-811 questions linked to 1Z0-811 fundamentals.
1Z0-811 scenario practice questions
Practise 1Z0-811 questions linked to 1Z0-811 scenario.
1Z0-811 troubleshooting practice questions
Practise 1Z0-811 questions linked to 1Z0-811 troubleshooting.
Practice this exam
Start a free 1Z0-811 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this 1Z0-811 question test?
Exception Handling and Development Tools — This question tests Exception Handling and Development Tools — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Inside the try block, set a boolean success flag to true upon completion; in the finally block, check the flag: if false, rollback; if true, commit. Additionally, catch specific exceptions, log them, and ensure rollback logic is invoked. — Option C is correct: Use a boolean flag inside the try block to indicate success; in the finally block, check the flag to decide whether to commit or rollback. This ensures that the transaction is only committed if no exception occurred. Additionally, catching specific exceptions (including RuntimeException) and logging them ensures proper handling. Option A is wrong because using a finally block to commit always commits even if an exception occurred, unless a flag is used. Option B is wrong because adding a separate RuntimeException catch before the generic Exception catch is syntactically possible but still commits in finally unless rollback is called. Option D is wrong because using throws pushes the problem to the caller without resolving the rollback requirement.
What should I do if I get this 1Z0-811 question wrong?
Identify which 1Z0-811 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
Keep practising
More 1Z0-811 practice questions
- A developer is troubleshooting a performance issue in a reporting application. A nested loop iterates over a large datas…
- A developer writes: boolean b = !true && false; What is the value of b?
- Given: int a = 10; int b = 20; boolean flag = a++ > 10 && ++b > 20; What are the values of a and b after execution?
- What is the value of the expression (10 > 5) && (3 < 2)?
- Which primitive data type should be used to store a single character?
- A developer writes: for(int i=0; i<10; i++) { if(i%2==0) continue; System.out.print(i); }. What is the output?
Last reviewed: Jun 23, 2026
This 1Z0-811 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-811 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.