- A
@property def _score(self): return self.score @_score.setter def _score(self, value): self.score = value
Why wrong: This creates infinite recursion because getter calls self.score which calls getter again.
- B
@property def score(self): return self.score @score.setter def score(self, value): self.score = value
Why wrong: Recursion: getter and setter call themselves.
- C
def get_score(self): return self._score def set_score(self, value): self._score = value score = property(get_score, set_score)
Why wrong: This works but does not include validation, though it is a valid property usage. However, question asks for getter and setter ensuring range, so validation is missing.
- D
@property def score(self): return self._score @score.setter def score(self, value): if 0 <= value <= 100: self._score = value
Correct pattern with private attribute.
Quick Answer
The correct answer is the code block using @property to define the getter and @score.setter to define the setter, with validation inside the setter to ensure the score stays between 0 and 100. This is correct because the @property decorator transforms a method into a managed attribute, allowing you to control access to an underlying private attribute like _score. The @score.setter decorator then attaches a setter method that runs validation logic—here, checking the range—before assigning the value, which prevents invalid data from being stored. On the PCAP exam, this tests your understanding of encapsulation and property decorator getter setter validation, a core concept for object-oriented programming in Python. A common trap is forgetting to use a private attribute (self._score) inside the setter; assigning to self.score would cause infinite recursion. Memory tip: think of @property as the gatekeeper and @score.setter as the bouncer—only values between 0 and 100 get past.
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 of the following is a correct use of the @property decorator to create a getter and setter for an attribute named 'score' that ensures score stays between 0 and 100?
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
@property def score(self): return self._score @score.setter def score(self, value): if 0 <= value <= 100: self._score = value
The @property decorator creates a getter method. The @score.setter decorator creates a setter that validates the value. Inside the setter, you should assign to a private attribute like _score to avoid recursion.
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.
- ✗
@property def _score(self): return self.score @_score.setter def _score(self, value): self.score = value
Why it's wrong here
This creates infinite recursion because getter calls self.score which calls getter again.
- ✗
@property def score(self): return self.score @score.setter def score(self, value): self.score = value
Why it's wrong here
Recursion: getter and setter call themselves.
- ✗
def get_score(self): return self._score def set_score(self, value): self._score = value score = property(get_score, set_score)
Why it's wrong here
This works but does not include validation, though it is a valid property usage. However, question asks for getter and setter ensuring range, so validation is missing.
- ✓
@property def score(self): return self._score @score.setter def score(self, value): if 0 <= value <= 100: self._score = value
Why this is correct
Correct pattern with private attribute.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
- Use explanations to understand the rule behind the answer.
TExam Day Tips
- Underline the problem statement mentally.
- 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 PCAP exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
- →
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
Related PCAP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Modules and Packages practice questions
Practise PCAP questions linked to Modules and Packages.
Strings practice questions
Practise PCAP questions linked to Strings.
Object-Oriented Programming practice questions
Practise PCAP questions linked to Object-Oriented Programming.
Exceptions and File I/O practice questions
Practise PCAP questions linked to Exceptions and File I/O.
PCAP fundamentals practice questions
Practise PCAP questions linked to PCAP fundamentals.
PCAP scenario practice questions
Practise PCAP questions linked to PCAP scenario.
PCAP troubleshooting practice questions
Practise PCAP questions linked to PCAP troubleshooting.
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: @property def score(self): return self._score @score.setter def score(self, value): if 0 <= value <= 100: self._score = value — The @property decorator creates a getter method. The @score.setter decorator creates a setter that validates the value. Inside the setter, you should assign to a private attribute like _score to avoid recursion.
What should I do if I get this PCAP question wrong?
Identify which PCAP exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
Keep practising
More PCAP practice questions
- Which TWO of the following are valid ways to raise an exception in Python?
- Match each Python operator to its precedence level (1=highest).
- Match each Python module to its purpose.
- Drag and drop the steps to create and activate a virtual environment in Python into the correct order.
- Drag and drop the steps to create a Python package with subpackages into the correct order.
- Drag and drop the steps to handle an exception in Python using try-except-finally into the correct order.
Last reviewed: Jun 24, 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.