Quick Answer
The answer is using `logging.exception()` inside an except block and `traceback.format_exc()` to capture the full traceback as a string. These are the two appropriate techniques for logging exception details properly because `logging.exception()` is the idiomatic Python method that automatically includes the full traceback of the current exception when called within an except block, while `traceback.format_exc()` provides a portable string representation of the entire stack trace that can be stored or logged manually. On the Certified Associate Python Programmer PCAP exam, this question tests your understanding of the `logging` module’s built-in exception handling versus manual traceback extraction, often appearing as a trap where beginners might choose `print(exception)` or `str(e)`, which lose the stack trace. A common memory tip is to remember that `logging.exception()` is the “all-in-one” tool for exception logging—it’s like a Swiss Army knife that gives you the traceback automatically, so you never need to call `traceback.format_exc()` unless you want to log the traceback separately from the exception message.
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 TWO of the following are appropriate techniques for logging exception details in Python? (Select exactly 2)
Using print(e.args)
Why wrong: Prints only arguments, not traceback.
Using traceback.format_exc()
Returns traceback string, suitable for logging.
Using sys.exc_info()
Why wrong: Returns tuple; requires manual formatting.
Using raise without argument
Why wrong: Re-raises, does not log.
Using logging.exception() inside except block
Standard method to log exception with traceback.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Using traceback.format_exc()
Option B is correct because `traceback.format_exc()` returns the full traceback as a string, which can be logged or printed to capture detailed exception context. Option E is correct because `logging.exception()` automatically includes the traceback of the current exception when called inside an `except` block, making it the idiomatic way to log exceptions in Python.
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.
Using print(e.args)
Why it's wrong here
Prints only arguments, not traceback.
Using traceback.format_exc()
Why this is correct
Returns traceback string, suitable for logging.
Related concept
Read the scenario before looking for a memorised answer.
Using sys.exc_info()
Why it's wrong here
Returns tuple; requires manual formatting.
Using raise without argument
Why it's wrong here
Re-raises, does not log.
Using logging.exception() inside except block
Why this is correct
Standard method to log exception with traceback.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Python Institute often tests the distinction between merely accessing exception data (like `e.args` or `sys.exc_info()`) and actually formatting or logging it properly, so candidates mistakenly think any function that touches exception info qualifies as a 'logging technique'.
Detailed technical explanation
Under the hood, `traceback.format_exc()` calls `sys.exc_info()` internally to obtain the current exception's traceback object, then formats it into a human-readable string using the same logic as Python's default exception printer. `logging.exception()` uses the `exc_info` parameter internally, setting it to `True` by default, which causes the logger to capture the traceback from the current exception context. In real-world production systems, using `logging.exception()` ensures that exception details are recorded with timestamps and log levels, which is critical for debugging without cluttering stdout.
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: Using traceback.format_exc() — Option B is correct because `traceback.format_exc()` returns the full traceback as a string, which can be logged or printed to capture detailed exception context. Option E is correct because `logging.exception()` automatically includes the traceback of the current exception when called inside an `except` block, making it the idiomatic way to log exceptions in Python.
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 →
Keep practising
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.