Quick Answer
The Liskov Substitution Principle is the correct answer because it ensures that a function like `calculate_area(shape)` works correctly when any subclass of `Shape`, such as `Circle` or `Square`, is passed in its place. This principle, a core part of the SOLID design principles, demands that subclasses honor the contract established by the superclass—here, the `area` method—so that substituting a subclass does not introduce errors or unexpected behavior. On the Certified Associate Python Programmer PCAP exam, this concept tests your understanding of polymorphism and proper inheritance design; a common trap is confusing LSP with simple method overriding, but LSP specifically requires that the subclass’s behavior remains consistent with the parent’s intent. To remember it, think of the “substitution test”: if swapping a subclass for its parent breaks the code, you’ve violated LSP.
This PCAP practice question tests your understanding of object-oriented programming. 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 Python class 'Shape' defines an abstract method 'area'. Subclasses 'Circle' and 'Square' implement 'area'. A function 'calculate_area(shape)' expects a 'Shape' instance. Which principle ensures that the function works correctly without knowing the specific subclass?
Interface Segregation Principle
Why wrong: ISP is about keeping interfaces small.
Liskov Substitution Principle
LSP ensures that any subclass can replace the base class without breaking the function.
Single Responsibility Principle
Why wrong: SRP is about each class having one responsibility.
Dependency Inversion Principle
Why wrong: DIP is about high-level modules not depending on low-level modules.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Liskov Substitution Principle
The Liskov Substitution Principle (LSP) states that objects of a superclass should be replaceable with objects of its subclasses without affecting the correctness of the program. In this scenario, 'calculate_area(shape)' accepts a 'Shape' instance, and because both 'Circle' and 'Square' are proper subtypes that honor the contract of the 'area' method, the function works correctly regardless of which subclass is passed. This is the core of LSP: substitutability without side effects.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Interface Segregation Principle
Why it's wrong here
ISP is about keeping interfaces small.
Liskov Substitution Principle
Why this is correct
LSP ensures that any subclass can replace the base class without breaking the function.
Related concept
Read the scenario before looking for a memorised answer.
Single Responsibility Principle
Why it's wrong here
SRP is about each class having one responsibility.
Dependency Inversion Principle
Why it's wrong here
DIP is about high-level modules not depending on low-level modules.
Common exam traps
Python Institute often tests LSP by presenting a scenario where a subclass overrides a method in a way that changes the expected behavior (e.g., raising an exception or returning a different type), and candidates mistakenly choose Interface Segregation or Dependency Inversion because they confuse 'substitutability' with 'abstraction' or 'interface design'.
Detailed technical explanation
Under the hood, LSP is enforced by ensuring that subclass methods do not strengthen preconditions or weaken postconditions relative to the base class. In Python, duck typing and the lack of compile-time type checking make LSP violations subtle—for example, a 'Square' subclass that raises a TypeError for negative side lengths while 'Shape.area' accepts any numeric input would break LSP. In real-world code, violating LSP often leads to runtime errors when using collections of polymorphic objects, such as iterating over a list of 'Shape' instances and calling 'area()' on each.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Object-Oriented Programming — study guide chapter
Learn the concepts, then practise the questions
Object-Oriented Programming practice questions
Targeted practice on this topic area only
All PCAP questions
511 questions across all exam domains
Certified Associate Python Programmer PCAP study guide
Full concept coverage aligned to exam objectives
PCAP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCAP questions linked to Modules and Packages.
Practise PCAP questions linked to Strings.
Practise PCAP questions linked to Object-Oriented Programming.
Practise PCAP questions linked to Exceptions and File I/O.
Practise PCAP questions linked to PCAP fundamentals.
Practise PCAP questions linked to PCAP scenario.
Practise PCAP questions linked to PCAP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Object-Oriented Programming — This question tests Object-Oriented Programming — Read the scenario before looking for a memorised answer..
The correct answer is: Liskov Substitution Principle — The Liskov Substitution Principle (LSP) states that objects of a superclass should be replaceable with objects of its subclasses without affecting the correctness of the program. In this scenario, 'calculate_area(shape)' accepts a 'Shape' instance, and because both 'Circle' and 'Square' are proper subtypes that honor the contract of the 'area' method, the function works correctly regardless of which subclass is passed. This is the core of LSP: substitutability without side effects.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Keep practising
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.