The correct approach is to catch the exception, log the full traceback, then raise a custom generic exception. This balances security and debugging by preserving the complete error details—including sensitive file paths—in the log for developers, while shielding end users from internal system information through a sanitized, generic exception. On the Certified Associate Python Programmer PCAP exam, this pattern tests your understanding of secure exception handling and the principle of least privilege in error management; a common trap is to either log without raising (which hides failures from users) or to re-raise the original exception (which leaks sensitive data). The key is to remember that logging is for developers, raising is for users. A useful memory tip: "Log the truth, raise the mask."
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 is working on a data pipeline that processes files from untrusted sources. The pipeline should catch and log any exception, but also ensure that sensitive information from the exception (e.g., file paths) is not exposed to end users. Which approach balances security and debugging?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Catch the exception, log the full traceback, then raise a custom generic exception.
Option C is correct because it balances security and debugging: the full traceback is logged for developers (preserving debugging details like file paths), while a custom generic exception is raised to end users, preventing sensitive information from being exposed. This approach follows the principle of least privilege for error handling, ensuring that internal details are not leaked to untrusted sources.
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.
✗
Catch the exception and re-raise the same exception.
Why it's wrong here
Re-raising may still expose sensitive details if unhandled.
✗
Catch the exception, log it, and suppress it silently.
Why it's wrong here
Suppressing silently hides errors from operators, making debugging difficult.
✓
Catch the exception, log the full traceback, then raise a custom generic exception.
Why this is correct
Logs details for developers, raises a safe exception to users.
Related concept
Read the scenario before looking for a memorised answer.
✗
Catch the exception and print it to the console.
Why it's wrong here
Exposes sensitive info to end users; not secure.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Python Institute often tests the distinction between logging exceptions for debugging versus exposing them to users, and the trap here is that candidates may choose Option A (re-raise) thinking it preserves the exception chain, but they overlook the security requirement to hide sensitive details from end users.
Detailed technical explanation
How to think about this question
In Python, the traceback object (via sys.exc_info() or traceback.format_exc()) captures the full call stack including local variables and file paths, which is essential for debugging but must be logged securely (e.g., to a file or logging service) rather than displayed. Raising a custom generic exception (e.g., RuntimeError('Processing failed')) ensures that the exception chain is preserved for programmatic handling while sanitizing the user-facing message. In real-world data pipelines, this pattern is critical for compliance with standards like GDPR or PCI-DSS, where exposing internal paths could lead to data breaches.
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.
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: Catch the exception, log the full traceback, then raise a custom generic exception. — Option C is correct because it balances security and debugging: the full traceback is logged for developers (preserving debugging details like file paths), while a custom generic exception is raised to end users, preventing sensitive information from being exposed. This approach follows the principle of least privilege for error handling, ensuring that internal details are not leaked to untrusted sources.
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.