Question 57 of 511
Exceptions and File I/OmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct choice is the bare `raise` statement inside the `except` block, as it re-raises the original exception while preserving its full traceback. This works because a bare `raise` without an argument in an exception handler automatically re-raises the exact exception instance that was caught, keeping the original call stack and error context intact—unlike `raise e`, which would create a new traceback. On the Certified Associate Python Programmer PCAP exam, this question tests your understanding of exception handling best practices, specifically the difference between re-raising with `raise` versus `raise e`. A common trap is thinking `raise e` is equivalent, but it resets the traceback, which can break debugging. Remember the memory tip: bare raise keeps the traceback blaze, while named raise starts a new traceback maze.

PCAP Exceptions and File I/O Practice Question

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.

A developer has a function that performs several operations and may raise different exceptions. The developer wants to catch a specific exception and then re-raise it after logging. Which code snippet correctly re-raises the same exception without losing its traceback?

Question 1mediummultiple choice
Full question →

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

except ValueError as e: log.error(e); raise

Option A is correct because using a bare `raise` statement inside an `except` block re-raises the original exception instance, preserving its full traceback. This is the standard Python idiom for logging an exception and then propagating it unchanged, ensuring that the original call stack and error context are not lost.

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.

  • except ValueError as e: log.error(e); raise

    Why this is correct

    Re-raises the same exception preserving traceback.

    Related concept

    Read the scenario before looking for a memorised answer.

  • except ValueError as e: log.error(e); return None

    Why it's wrong here

    Returns without re-raising, so the exception is handled silently.

  • except ValueError as e: log.error(e); raise ValueError('New')

    Why it's wrong here

    Creates a new ValueError, losing original context and traceback.

  • except ValueError as e: log.error(e); pass

    Why it's wrong here

    Suppresses the exception entirely, which may not be intended.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the distinction between a bare `raise` (which preserves the original exception and traceback) and `raise SomeException(...)` (which creates a new exception and loses the original context), leading candidates to incorrectly choose the latter when they think they need to 're-raise' by specifying the exception class again.

Detailed technical explanation

How to think about this question

In CPython, the `raise` statement without arguments in an `except` block uses the `sys.exc_info()` triple (type, value, traceback) that was saved when the exception was caught, and it restores the original traceback object. This is critical in logging frameworks where you want to record the error but still let higher-level handlers deal with it; using `raise e` would also work but is slightly less explicit about preserving the traceback, though both are functionally equivalent in modern Python.

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?

Exceptions and File I/O — This question tests Exceptions and File I/O — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: except ValueError as e: log.error(e); raise — Option A is correct because using a bare `raise` statement inside an `except` block re-raises the original exception instance, preserving its full traceback. This is the standard Python idiom for logging an exception and then propagating it unchanged, ensuring that the original call stack and error context are not lost.

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.