The correct choice is to override __init__ to accept a message and call super().__init__(message). This is essential because the built-in Exception class stores any passed message in its args attribute, and its default __str__ method relies on that attribute to display the error text when the exception is caught and printed. Without explicitly calling the parent constructor, your custom exception class would not inherit this message-handling behavior, and the message would be lost or not shown. On the Certified Associate Python Programmer PCAP exam, this tests your understanding of proper inheritance in Python’s exception hierarchy, often appearing as a multiple-choice trap where a candidate might override __str__ instead of __init__. The common mistake is forgetting that the base class already handles string representation, so you only need to ensure the message reaches it. Memory tip: “Init it to pass it”—override __init__ to accept the message, then pass it up with super().__init__().
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.
A developer implements a custom exception class `DataError` that inherits from `Exception`. Which method override is essential to ensure the exception message is properly displayed when caught?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Override __init__ to accept a message and call super().__init__(message).
Option A is correct because the `Exception` class's `__init__` method stores the message argument in the `args` attribute, which is used by the default `__str__` method to display the message. By overriding `__init__` to accept a message and call `super().__init__(message)`, the custom exception properly passes the message to the base class, ensuring it is displayed when caught and printed.
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.
✓
Override __init__ to accept a message and call super().__init__(message).
Why this is correct
This ensures the message is stored and displayed.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set the __cause__ attribute in __init__.
Why it's wrong here
__cause__ is for exception chaining, not message display.
✗
Override __str__ to return a formatted string.
Why it's wrong here
Exception already provides __str__ if message is passed to init.
✗
Override __repr__ to return a detailed representation.
Why it's wrong here
__repr__ is not used for displaying exception messages.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Python Institute often tests the misconception that you must override `__str__` to display a custom message, when in fact the base `Exception.__init__` handles message storage and display automatically if called correctly.
Detailed technical explanation
How to think about this question
The `Exception` base class stores positional arguments passed to `__init__` in the `args` attribute (a tuple). The default `__str__` method returns `str(self.args[0])` if there is exactly one argument, otherwise `str(self.args)`. This design allows custom exceptions to simply delegate to `super().__init__(message)` without needing to override `__str__` or `__repr__`. In real-world scenarios, failing to call `super().__init__()` can lead to empty or misleading error messages, especially when using logging frameworks that rely on `str(exception)`.
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.
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: Override __init__ to accept a message and call super().__init__(message). — Option A is correct because the `Exception` class's `__init__` method stores the message argument in the `args` attribute, which is used by the default `__str__` method to display the message. By overriding `__init__` to accept a message and call `super().__init__(message)`, the custom exception properly passes the message to the base class, ensuring it is displayed when caught and printed.
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 →
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. A developer is implementing a custom exception for invalid data. Which class should the custom exception inherit from?
medium
A.RuntimeError
B.ArithmeticError
C.BaseException
✓ D.Exception
Why D: Option D is correct because the `Exception` class is the base class for all built-in, non-system-exiting exceptions in Python. Custom exceptions should inherit from `Exception` (or one of its subclasses) to ensure they are caught by generic `except Exception:` handlers and integrate properly with Python's exception hierarchy, while avoiding the system-exiting exceptions derived from `BaseException`.
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.
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.
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.