Question 172 of 169
Forcing Method Override Using NotImplementedError in Python
A developer creates a Python class with a method that is intended to be overridden in subclasses. Which approach best ensures that the method is not accidentally called on the base class?
Quick Answer
The correct approach is to raise NotImplementedError inside the method body. This is the standard Python idiom for forcing method override without importing the abc module, because it creates an explicit runtime contract: any subclass that fails to override the method will trigger an immediate, clear error when the method is called, preventing accidental use of a base implementation that should never run. On the Certified Associate Python Programmer PCAP exam, this pattern tests your understanding of polymorphism and inheritance enforcement—a common trap is confusing NotImplementedError with the abc.ABCMeta decorator, but the exam expects you to know that raising NotImplementedError is the lightweight, built-in way to signal an unimplemented method. A useful memory tip: think of NotImplementedError as a “red flag” that forces subclasses to provide their own version, or else the code crashes loudly at runtime, making bugs impossible to ignore.
⚠ Common exam trap
Python Institute often tests the distinction between documentation-based approaches (comments) and runtime enforcement (exceptions), leading candidates to mistakenly choose a comment or 'pass' as sufficient for preventing accidental base class usage.
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
✓
Raise NotImplementedError inside the method body
Raising NotImplementedError inside the base class method is the standard Python idiom for defining an abstract-like method that must be overridden in subclasses. If a subclass fails to override the method and it is called, Python will raise an explicit error at runtime, preventing accidental use of the base implementation. This approach enforces the contract that the method is intended only for subclasses, without requiring the `abc` module.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use 'pass' as the method body
Why it's wrong here
pass does nothing and allows accidental calls.
- ✗
Delete the method from the base class using 'del'
Why it's wrong here
Deleting the method would prevent any call, including from subclasses.
- ✗
Add a comment '# override in subclass' inside the method body
Why it's wrong here
Comments do not enforce overriding.
- ✓
Raise NotImplementedError inside the method body
Why this is correct
Raising NotImplementedError clearly signals the method must be overridden.
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 →
Same concept, more angles
1 more way 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. A developer is designing a class hierarchy for a library system. They want to ensure that a method 'borrow' in the base class 'Item' can be overridden by subclasses like 'Book' and 'DVD', but the base implementation should not be callable directly. Which approach best achieves this?
medium- ✓ A.Define borrow with raise NotImplementedError and override in subclasses
- B.Define borrow as a static method and override in subclasses
- C.Define borrow as a class method and override in subclasses
- D.Define borrow with pass and let subclasses override
Why A: Raising `NotImplementedError` in the base class `Item.borrow` makes the method abstract in practice: it cannot be called directly without causing an error, forcing subclasses like `Book` and `DVD` to provide their own override. This pattern enforces that the base implementation is never invoked accidentally, while still allowing polymorphic dispatch through inheritance.
Last reviewed: Jun 30, 2026
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.