Question 325 of 511
Object-Oriented ProgramminghardMultiple SelectObjective-mapped

Quick Answer

The correct answer is that name mangling is applied to attributes that start with two underscores but do not end with two underscores. This transformation works because Python’s compiler rewrites such attribute names at definition time—for example, `__attribute` inside class `MyClass` becomes `_MyClass__attribute`—which prevents accidental name collisions in subclasses without enforcing true privacy. On the Certified Associate Python Programmer PCAP exam, this concept tests your understanding of how Python handles attribute access in inheritance hierarchies, often appearing in multiple-choice questions that ask you to identify which attributes get mangled. A common trap is confusing name mangling with runtime attribute hiding; remember that the mangling is purely a compile-time renaming mechanism, not a security feature. For a quick memory tip, think of the double underscore as a “double lock” that adds the class name as a prefix, but only if the name doesn’t end with the same double underscore—so `__method__` stays untouched.

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.

Which TWO statements about Python's name mangling are correct?

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

The mangled name format is _ClassName__attribute.

Option B is correct because Python's name mangling transforms an attribute name like `__attribute` defined in a class `MyClass` into `_MyClass__attribute`. This mechanism is specifically designed to avoid name clashes in subclasses, not to enforce privacy. The transformation is done by the compiler at definition time, not at runtime.

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.

  • Name mangling applies to all method names that start with a single underscore.

    Why it's wrong here

    Only double underscores trigger mangling.

  • The mangled name format is _ClassName__attribute.

    Why this is correct

    Correct.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Name mangling prevents external code from accessing the attribute entirely.

    Why it's wrong here

    It only renames; still accessible if you know the mangled name.

  • Name mangling is applied to attributes that start with two underscores but do not end with two underscores.

    Why this is correct

    Correct.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Name mangling occurs at runtime.

    Why it's wrong here

    It occurs at compile time (class definition).

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the misconception that name mangling provides true access control (like private in Java), when in fact it is only a name transformation that can be bypassed by using the mangled name directly.

Detailed technical explanation

How to think about this question

Name mangling is implemented in the Python compiler by replacing each identifier starting with two underscores (and not ending with two underscores) with `_ClassName__identifier`. This is a lexical transformation that happens during class definition, so the mangled name is stored in the class's `__dict__`. A common subtlety is that mangling does not occur for names that end with two underscores (like `__init__`), as those are reserved for Python's special methods. In practice, this helps prevent accidental overriding of attributes in subclasses, but it is not a security feature.

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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

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: The mangled name format is _ClassName__attribute. — Option B is correct because Python's name mangling transforms an attribute name like `__attribute` defined in a class `MyClass` into `_MyClass__attribute`. This mechanism is specifically designed to avoid name clashes in subclasses, not to enforce privacy. The transformation is done by the compiler at definition time, not at runtime.

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.