Question 507 of 511
Object-Oriented ProgrammingmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to use a private method with a double underscore prefix, such as `__method`. This works because Python’s name mangling mechanism automatically renames the method to `_ClassName__method` at compile time, effectively binding it to the specific class where it is defined. As a result, any attempt to override `__method` in a subclass will create a new, distinct method rather than replacing the original, preventing method override in subclasses. On the PCAP exam, this concept tests your understanding of encapsulation and inheritance, often appearing as a trick where candidates confuse single underscores (convention only) with double underscores (enforced mangling). A common trap is assuming Python has true private members like Java; instead, name mangling is a syntactic renaming that discourages but does not block access. Remember the mnemonic: “Double underscore, double trouble for overrides—mangling makes the method stick to its class.”

PCAP Object-Oriented Programming Practice Question

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 team is using inheritance but wants to prevent a method from being overridden in subclasses. What Python feature can enforce this?

Question 1mediummultiple choice
Study the full Python automation breakdown →

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

Use a private method with double underscore prefix (__method).

Option A is correct because in Python, prefixing a method name with double underscores (e.g., `__method`) triggers name mangling, which renames the method to `_ClassName__method` at compile time. This prevents subclasses from accidentally overriding the method, as the mangled name is unique to the class where it is defined, effectively making it private and non-overridable in subclasses.

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.

  • Use a private method with double underscore prefix (__method).

    Why this is correct

    Name mangling makes the method harder to override accidentally, though it can still be overridden with the mangled name.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use a @final decorator.

    Why it's wrong here

    Python does not have a built-in @final decorator.

  • Use @staticmethod.

    Why it's wrong here

    Static methods can still be overridden in subclasses.

  • Use @abstractmethod.

    Why it's wrong here

    Abstract methods must be overridden, not prevented.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the misconception that `@final` is a built-in Python decorator for preventing method overriding, but Python does not enforce `@final` at runtime, making the double underscore prefix the correct answer for runtime prevention.

Detailed technical explanation

How to think about this question

Name mangling in Python is a compile-time transformation that adds the class name to the method name (e.g., `__method` becomes `_ClassName__method`), making it harder to accidentally override but not impossible (a subclass can still access the mangled name). This is commonly used in frameworks like Django or ORMs to avoid method name collisions in deep inheritance hierarchies, where a base class defines internal helper methods that should not be overridden by subclasses.

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?

Object-Oriented Programming — This question tests Object-Oriented Programming — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use a private method with double underscore prefix (__method). — Option A is correct because in Python, prefixing a method name with double underscores (e.g., `__method`) triggers name mangling, which renames the method to `_ClassName__method` at compile time. This prevents subclasses from accidentally overriding the method, as the mangled name is unique to the class where it is defined, effectively making it private and non-overridable in subclasses.

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.