Question 231 of 511
Exceptions and File I/OeasyMultiple SelectObjective-mapped

Quick Answer

The answer is ValueError and FileNotFoundError. Both are built-in exceptions in Python, meaning they are part of the language’s standard exception hierarchy and require no import to use. ValueError is raised when a function receives an argument of the correct type but an inappropriate value, such as attempting int('abc'), while FileNotFoundError occurs when an operation tries to access a file that does not exist at the specified path. On the Certified Associate Python Programmer PCAP exam, identifying built-in exceptions tests your understanding of Python’s core exception classes versus those that must be imported from modules like os or sys. A common trap is confusing FileNotFoundError with IOError, but remember that FileNotFoundError is a direct subclass of OSError and is raised automatically by open() when the file is missing. For a memory tip, think of ValueError as a “wrong value, right type” error, and FileNotFoundError as the “missing file” error—both are always available without any import statement.

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.

Which TWO of the following are built-in exceptions in Python? (Select exactly 2.)

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

ValueError

ValueError is a built-in exception in Python, raised when a built-in operation or function receives an argument with the correct type but an inappropriate value, such as int('abc'). It is part of Python's standard exception hierarchy and does not require any import.

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.

  • InputError

    Why it's wrong here

    InputError is not a built-in exception in Python; it may be defined in some libraries.

  • ValueError

    Why this is correct

    ValueError is a built-in exception raised when a function gets an argument of correct type but inappropriate value.

    Related concept

    Read the scenario before looking for a memorised answer.

  • DataError

    Why it's wrong here

    DataError is not a built-in exception; it is not part of the standard library.

  • FileNotFoundError

    Why this is correct

    FileNotFoundError is a built-in exception raised when trying to open a non-existent file.

    Related concept

    Read the scenario before looking for a memorised answer.

  • CustomError

    Why it's wrong here

    CustomError is not a built-in exception; user-defined exceptions are not built-in.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests candidates by including plausible-sounding exception names like InputError or DataError that mimic real-world patterns but are not part of Python's built-in exception hierarchy, leading candidates to confuse custom or third-party exceptions with standard ones.

Detailed technical explanation

How to think about this question

Python's built-in exceptions are defined in the 'exceptions' module and automatically available in the global namespace. ValueError inherits from Exception and is commonly raised by functions like int(), float(), and math.sqrt() when the argument is valid in type but not in value. FileNotFoundError, introduced in Python 3.3, is a subclass of OSError and is raised when a file or directory is requested but cannot be found, which is critical for robust file I/O error handling in production code.

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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

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: ValueError — ValueError is a built-in exception in Python, raised when a built-in operation or function receives an argument with the correct type but an inappropriate value, such as int('abc'). It is part of Python's standard exception hierarchy and does not require any import.

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.