Polymorphism and Method Overriding in Python | Certified Associate Python Programmer
A company needs to model different types of employees. They have a base class `Employee` with a method `calculate_pay()`. For hourly employees, pay = hours * rate; for salaried employees, pay = salary. Which design approach is most appropriate?
Quick Answer
The correct design approach is to create subclasses `HourlyEmployee` and `SalariedEmployee` that override `calculate_pay()`. This is the most appropriate because it applies polymorphism through method overriding: each subclass provides its own specific implementation of the method while sharing the same interface from the base `Employee` class. This design allows calling code to treat all employee types uniformly, invoking `calculate_pay()` on any employee object without needing to know the concrete type. On the Certified Associate Python Programmer PCAP exam, this scenario tests your understanding of polymorphism and method overriding as core object-oriented principles, often appearing in questions about inheritance hierarchies and the Open/Closed Principle. A common trap is choosing a single conditional statement inside the base class, which violates extensibility and defeats polymorphism’s purpose. Memory tip: think “same method name, different behavior per subclass” — that’s overriding in action.
⚠ Common exam trap
Python Institute often tests the distinction between using inheritance with method overriding versus using conditionals or static methods, and the trap here is that candidates may think a single class with `if` statements is simpler and therefore better, missing the long-term maintenance and extensibility advantages of polymorphism.
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
✓
Create subclasses `HourlyEmployee` and `SalariedEmployee` that override `calculate_pay()`.
It applies polymorphism through method overriding: each subclass (`HourlyEmployee`, `SalariedEmployee`) provides its own implementation of `calculate_pay()`, allowing the calling code to treat all employees uniformly via the base class interface. This adheres to the Open/Closed Principle and keeps the design extensible without modifying existing code when new employee types are added.
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 a `@staticmethod` inside `Employee` to compute pay based on a type parameter.
Why it's wrong here
A static method cannot dispatch on instance state, so pay logic would need a type parameter rather than polymorphic overriding of calculate_pay(). Static helpers suit pure, stateless utilities like unit conversion, not behaviour that varies per subclass.
- ✗
Define a module-level function that takes an employee object and computes pay.
Why it's wrong here
A module-level function bypasses the base class's calculate_pay() contract, so callers cannot rely on polymorphic dispatch through Employee references. Free functions suit stateless transformations applied to external data, not behaviour owned by an object hierarchy.
- ✓
Create subclasses `HourlyEmployee` and `SalariedEmployee` that override `calculate_pay()`.
Why this is correct
Subclasses overriding `calculate_pay()` let each employee type supply its own formula, so hourly pay computes hours × rate while salaried returns the fixed salary. This satisfies the stem's requirement to model distinct employee types sharing one interface, since Python dispatches the overridden method polymorphically at runtime based on the instance's actual class.
- ✗
Use a single `Employee` class with conditional statements to differentiate pay types.
Why it's wrong here
Conditional branching inside one class forces edits whenever a new pay type appears, rather than letting subclasses override calculate_pay(). A single class with conditionals fits small, fixed, non-extensible value sets where polymorphism would add needless classes.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PCAP question from scratch — 421 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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 team is developing a system that must handle different types of documents (PDF, Word, etc.). Each document type has a unique parsing method. To avoid massive conditional logic, which OOP concept should be applied?
medium- ✓ A.Polymorphism
- B.Encapsulation
- C.Inheritance
- D.Abstraction
Why A: Polymorphism allows different document types (PDF, Word, etc.) to be treated uniformly through a common interface (e.g., a `parse()` method) while each class implements its own parsing logic. This eliminates the need for conditional statements (like `if type == 'PDF'`) because the correct method is resolved at runtime via dynamic dispatch, which is exactly what the team needs to avoid massive conditional logic.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.