Question 393 of 511
Exceptions and File I/OhardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is OSError, because it is the base class for all I/O-related exceptions in Python 3, including FileNotFoundError and PermissionError, while excluding KeyboardInterrupt and SystemExit which inherit directly from BaseException. This distinction matters because KeyboardInterrupt and SystemExit are designed to bypass the normal Exception hierarchy, ensuring that critical program termination signals are never accidentally swallowed by a broad except clause. On the Certified Associate Python Programmer PCAP exam, this question tests your understanding of the exception class hierarchy and the common trap of using a bare except: or catching Exception, which would inadvertently block interrupts. A reliable memory tip is to remember that OSError is the "umbrella" for file and I/O errors, but it sits under Exception, not BaseException, so it lets Ctrl+C and sys.exit() pass through untouched.

PCAP Exceptions and File I/O Practice Question

This PCAP practice question tests your understanding of exceptions and file i/o. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.

A Python application processes user-uploaded files. The requirement is to catch any I/O-related exception while reading the file, but not to catch KeyboardInterrupt or SystemExit. Which exception type should be caught?

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

OSError

Option A is correct because `OSError` is the base class for all I/O-related exceptions in Python 3, including file reading errors like `FileNotFoundError` and `PermissionError`. It does not catch `KeyboardInterrupt` or `SystemExit`, which inherit directly from `BaseException`, not `Exception`. This makes `OSError` the precise choice for catching I/O errors while allowing program termination signals to propagate.

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.

  • OSError

    Why this is correct

    Covers I/O errors while avoiding system-exiting exceptions.

    Related concept

    Read the scenario before looking for a memorised answer.

  • IOError

    Why it's wrong here

    Deprecated in Python 3; use OSError instead.

  • Exception

    Why it's wrong here

    Catches all built-in exceptions, including unintended ones like KeyboardInterrupt.

  • BaseException

    Why it's wrong here

    Catches everything, even SystemExit and KeyboardInterrupt.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the Python 3 exception hierarchy change where `IOError` is no longer a separate class but an alias of `OSError`, tempting candidates to pick the familiar `IOError` from Python 2 instead of the correct `OSError`.

Detailed technical explanation

How to think about this question

In Python 3, the exception hierarchy was reorganized: `IOError`, `EnvironmentError`, and `WindowsError` were merged into `OSError` (PEP 3151). This means `OSError` is the single class for all system-related errors, including file I/O, network, and permission issues. A real-world scenario is a file upload service that must catch `OSError` to handle disk full or permission denied errors gracefully, while still allowing `KeyboardInterrupt` (Ctrl+C) to terminate the process cleanly.

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: OSError — Option A is correct because `OSError` is the base class for all I/O-related exceptions in Python 3, including file reading errors like `FileNotFoundError` and `PermissionError`. It does not catch `KeyboardInterrupt` or `SystemExit`, which inherit directly from `BaseException`, not `Exception`. This makes `OSError` the precise choice for catching I/O errors while allowing program termination signals to propagate.

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

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.