Question 87 of 509
Java Basics and SyntaxhardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is that a catch block can only handle one type of exception. This is enforced by Java’s syntax, where each catch clause is declared with a single exception type parameter, such as `catch (IOException e)`, meaning it can only catch that specific exception or its subclasses. On the Oracle Java Foundations 1Z0-811 exam, this rule tests your understanding of basic exception handling structure, often appearing in questions that try to trick you with multi-catch syntax or the idea that a single catch block could handle multiple unrelated exceptions. A common trap is confusing the multi-catch feature introduced in Java 7, which uses a pipe symbol like `catch (IOException | SQLException e)`, but even that is still a single catch block with a union of types—not a block that handles multiple types independently. To remember: think of a catch block as a single-slot mailbox—it only accepts one type of letter (exception) at a time.

1Z0-811 Java Basics and Syntax Practice Question

This 1Z0-811 practice question tests your understanding of java basics and syntax. 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 statement about try-catch is true?

Question 1hardmultiple choice
Full question →

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

A catch block can only handle one type of exception.

Option D is correct because in Java, a catch block is defined with a single exception type parameter, meaning it can only handle one specific type of exception (or its subclasses if the parameter is a superclass). This is enforced by the language syntax: `catch (ExceptionType e)` allows only one exception type per catch clause.

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 finally block is always required.

    Why it's wrong here

    Not required; catch alone is sufficient.

  • A try block without a catch or finally is legal.

    Why it's wrong here

    Illegal; must have at least one catch or finally.

  • A try block can have multiple catch blocks for the same exception type.

    Why it's wrong here

    Not allowed; duplicate catch types cause error.

  • A catch block can only handle one type of exception.

    Why this is correct

    Correct: each catch block handles one exception type (unless multi-catch).

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Oracle often tests the misconception that a catch block can handle multiple unrelated exception types without using multi-catch syntax, leading candidates to incorrectly select option D as false, when in fact a single catch block can only handle one exception type (or a union via multi-catch, but that is still a single catch block with a disjunctive type).

Detailed technical explanation

How to think about this question

Under the hood, the Java compiler enforces that catch blocks are checked in order, and if a catch parameter type is a subclass of a previous catch's type, the second block is unreachable and causes a compilation error. In real-world scenarios, you might catch multiple exception types using a multi-catch clause (e.g., `catch (IOException | SQLException e)`) introduced in Java 7, but each individual catch block still handles exactly one exception type (or a union of types via the multi-catch syntax).

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-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.

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.

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.

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?

Java Basics and Syntax — This question tests Java Basics and Syntax — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: A catch block can only handle one type of exception. — Option D is correct because in Java, a catch block is defined with a single exception type parameter, meaning it can only handle one specific type of exception (or its subclasses if the parameter is a superclass). This is enforced by the language syntax: `catch (ExceptionType e)` allows only one exception type per catch clause.

What should I do if I get this 1Z0-811 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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More 1Z0-811 practice questions

Last reviewed: Jun 30, 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.

Loading comments…

Sign in to join the discussion.

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.