Question 411 of 511
Exceptions and File I/OhardMultiple SelectObjective-mapped

Quick Answer

The answer is that the output of this code is 'Index'. This is correct because Python’s exception handling follows a hierarchical subclass relationship: `IndexError` is a direct subclass of `LookupError`, and when an exception is raised, Python checks the `except` clauses in the order they appear. Since the `except IndexError` block is listed first, it catches the raised exception before the more general `except LookupError` block is ever considered, so only 'Index' prints. On the Certified Associate Python Programmer PCAP exam, this tests your understanding of the Python exception hierarchy and the importance of ordering except clauses from most specific to most general. A common trap is assuming a parent class handler will override a child class handler when both are present; in reality, the first matching clause wins. To remember this, think of the hierarchy as a family tree: the child (IndexError) gets the first chance to handle its own problem before the parent (LookupError) steps in.

PCAP Exceptions and File I/O Practice Question

This PCAP practice question tests your understanding of exceptions and file i/o. 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.

Consider the following code snippet:

x = [1, 2, 3]

try:
    print(x[5])

except IndexError:

print('Index')

except LookupError:

print('Lookup')

Which THREE statements about this code are correct? (Select exactly 3.)

Question 1hardmulti select
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

If the line with IndexError is removed, then LookupError will catch the exception.

Option B is correct because when the IndexError handler is removed, the exception propagates to the next matching except clause. Since IndexError is a subclass of LookupError, the LookupError handler will catch the raised IndexError. This demonstrates the hierarchical nature of exception handling in Python, where a more general exception class can catch exceptions of its subclasses.

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.

  • The code will print 'Lookup' because LookupError is more general.

    Why it's wrong here

    The first matching except executes; IndexError matches before LookupError.

  • If the line with IndexError is removed, then LookupError will catch the exception.

    Why this is correct

    Without the specific handler, the next matching handler (LookupError) will catch it.

    Related concept

    Read the scenario before looking for a memorised answer.

  • IndexError is a subclass of LookupError.

    Why this is correct

    Yes, IndexError inherits from LookupError.

    Related concept

    Read the scenario before looking for a memorised answer.

  • If the code were accessing a dictionary key, LookupError would catch KeyError.

    Why this is correct

    KeyError is also a subclass of LookupError.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The output of this code is 'Index'.

    Why this is correct

    The IndexError handler catches the exception and prints 'Index'.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the order of except clauses and the exception hierarchy, trapping candidates who assume that a more general exception handler will always catch an exception first, or who forget that Python uses first-match semantics rather than best-match.

Detailed technical explanation

How to think about this question

Python's exception hierarchy is rooted in BaseException, with Exception as the base for all built-in non-system-exiting exceptions. LookupError is the base class for IndexError and KeyError, among others. When an exception is raised, Python walks through the except clauses in order and executes the first matching one based on the exception's class or any of its superclasses. This means that placing a more specific exception (like IndexError) before a more general one (like LookupError) is essential for correct handling; reversing the order would cause the general handler to catch all LookupError subclasses, making the specific handler unreachable.

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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

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 PCAP 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 PCAP 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 PCAP question test?

Exceptions and File I/O — This question tests Exceptions and File I/O — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: If the line with IndexError is removed, then LookupError will catch the exception. — Option B is correct because when the IndexError handler is removed, the exception propagates to the next matching except clause. Since IndexError is a subclass of LookupError, the LookupError handler will catch the raised IndexError. This demonstrates the hierarchical nature of exception handling in Python, where a more general exception class can catch exceptions of its subclasses.

What should I do if I get this PCAP 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

Same concept, more angles

1 more ways this is tested on PCAP

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 of the following exception classes is NOT a direct subclass of Exception in Python?

hard
  • A.IOError
  • B.SystemExit
  • C.StopIteration
  • D.ValueError

Why B: SystemExit is not a direct subclass of Exception; it inherits from BaseException instead. This is because SystemExit, along with KeyboardInterrupt and GeneratorExit, is intended to signal that the interpreter should exit, and catching it with a generic except Exception clause would be inappropriate. All other options (IOError, StopIteration, ValueError) are direct subclasses of Exception.

Keep practising

More PCAP 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 PCAP practice question is part of Courseiva's free Python Institute 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 PCAP exam.