Quick Answer
The correct answer is that the `finally` block always executes, regardless of exceptions. This guarantee holds because Python’s exception handling model is designed to run the `finally` clause after the `try` and `except` blocks complete, no matter what—whether an exception is raised, caught, or even if a `return`, `break`, or `continue` statement is encountered inside the `try` block. On the Certified Associate Python Programmer PCAP exam, this concept tests your understanding of cleanup guarantees and resource management, often appearing in questions that present tricky scenarios like a `return` inside `try` followed by a `finally` block. A common trap is assuming `finally` won’t run if an unhandled exception occurs, but in reality it executes before the exception propagates. Remember the mnemonic: “Finally is final—it always fires, no exceptions.”
This PCAP practice question tests your understanding of exceptions and file i/o. 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 statements about the `finally` block is true?
It executes only if no exception is raised.
Why wrong: Finally always executes.
It does not execute if a return statement is in try block.
Why wrong: Finally executes even after return.
It executes only if an exception is raised.
Why wrong: Finally always executes.
It always executes, regardless of exceptions.
Finally is guaranteed to run.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
It always executes, regardless of exceptions.
Option D is correct because the `finally` block in Python is designed to always execute after the `try` and `except` blocks, regardless of whether an exception was raised or not. This includes cases where a `return`, `break`, or `continue` statement is executed in the `try` block, or even if an unhandled exception occurs. The `finally` block is guaranteed to run before the function returns or the exception propagates, ensuring cleanup actions like closing files or releasing resources.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
It executes only if no exception is raised.
Why it's wrong here
Finally always executes.
It does not execute if a return statement is in try block.
Why it's wrong here
Finally executes even after return.
It executes only if an exception is raised.
Why it's wrong here
Finally always executes.
It always executes, regardless of exceptions.
Why this is correct
Finally is guaranteed to run.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Python Institute often tests the misconception that a `return` statement in the `try` block prevents the `finally` block from executing, but in Python, the `finally` block always runs before the function returns, making this a common trap for candidates who confuse Python's behavior with that of other languages.
Detailed technical explanation
Under the hood, Python's `finally` block is implemented as part of the exception handling mechanism that uses a stack of frames and cleanup handlers. Even if a `return` statement is executed in the `try` block, the interpreter saves the return value, runs the `finally` block, and then returns the saved value. A real-world scenario is closing a database connection in a `finally` block to ensure it is always released, even if an error occurs during query processing.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Exceptions and File I/O — study guide chapter
Learn the concepts, then practise the questions
Exceptions and File I/O 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCAP questions linked to Modules and Packages.
Practise PCAP questions linked to Strings.
Practise PCAP questions linked to Object-Oriented Programming.
Practise PCAP questions linked to Exceptions and File I/O.
Practise PCAP questions linked to PCAP fundamentals.
Practise PCAP questions linked to PCAP scenario.
Practise PCAP questions linked to PCAP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Exceptions and File I/O — This question tests Exceptions and File I/O — Read the scenario before looking for a memorised answer..
The correct answer is: It always executes, regardless of exceptions. — Option D is correct because the `finally` block in Python is designed to always execute after the `try` and `except` blocks, regardless of whether an exception was raised or not. This includes cases where a `return`, `break`, or `continue` statement is executed in the `try` block, or even if an unhandled exception occurs. The `finally` block is guaranteed to run before the function returns or the exception propagates, ensuring cleanup actions like closing files or releasing resources.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Same concept, more angles
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 developer wants to ensure that a file is always closed, even if an exception occurs, without using the 'with' statement. Which approach correctly achieves this?
mediumWhy B: Option B is correct because the `finally` block is guaranteed to execute regardless of whether an exception occurs in the `try` block. This ensures that `f.close()` is always called, properly releasing the file resource. The `with` statement is not used, but the `try...finally` construct provides the same deterministic cleanup behavior.
Last reviewed: Jun 30, 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.