The correct approach is to declare the attribute as `self.__balance` and provide a getter method. This works because prefixing an attribute with double underscores triggers Python’s name mangling, which internally renames `__balance` to `_BankAccount__balance`, effectively hiding it from direct external access while still allowing a getter method to retrieve the value. On the Certified Associate Python Programmer PCAP exam, this tests your understanding of encapsulation and the distinction between weak private attributes and true privacy—a common trap is confusing single underscores (which are merely a convention) with double underscores (which enforce name mangling). Remember that Python does not enforce true privacy, so this idiom is the standard way to implement a private instance attribute with getter for controlled access. A useful memory tip: think of the double underscore as a “double lock” that mangles the name, making it harder to accidentally access from outside the class.
PCAP Object-Oriented Programming Practice Question
This PCAP practice question tests your understanding of object-oriented programming. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 developer wants to ensure that an attribute 'balance' of a BankAccount class cannot be accessed directly from outside the class but can be accessed through a method. Which approach should be used?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Declare 'self.__balance' and provide a getter method
Option D is correct because prefixing the attribute with double underscores (`__balance`) triggers Python's name mangling, which renames the attribute to `_BankAccount__balance` at runtime. This prevents direct access from outside the class (e.g., `obj.balance` raises an `AttributeError`), while a getter method (e.g., `get_balance()`) can still retrieve the value. This is the standard Python idiom for achieving 'weak' private encapsulation in OOP.
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.
✗
Declare 'self.balance' as a class variable
Why it's wrong here
Class variable is also public and directly accessible.
✗
Declare 'self.balance' and provide a getter method
Why it's wrong here
Public attribute can be accessed directly without the getter.
✗
Declare 'self._balance' and provide a getter method
Why it's wrong here
Single underscore is a naming convention only, does not prevent direct access.
✓
Declare 'self.__balance' and provide a getter method
Why this is correct
Double underscore makes attribute private via name mangling, and getter provides controlled access.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Python Institute often tests the distinction between single underscore (`_`) as a convention versus double underscore (`__`) as name mangling, and candidates mistakenly believe that a single underscore provides actual access restriction.
Detailed technical explanation
How to think about this question
Name mangling in Python transforms `self.__balance` to `self._BankAccount__balance` at compile time, making it harder to accidentally access from subclasses or external code. However, it is not true private encapsulation (unlike Java's `private`); a determined user can still access the mangled name directly (e.g., `obj._BankAccount__balance`). This mechanism is primarily designed to avoid attribute name collisions in inheritance hierarchies, not to enforce security.
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.
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: Declare 'self.__balance' and provide a getter method — Option D is correct because prefixing the attribute with double underscores (`__balance`) triggers Python's name mangling, which renames the attribute to `_BankAccount__balance` at runtime. This prevents direct access from outside the class (e.g., `obj.balance` raises an `AttributeError`), while a getter method (e.g., `get_balance()`) can still retrieve the value. This is the standard Python idiom for achieving 'weak' private encapsulation in OOP.
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 →
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.
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.