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

Quick Answer

The correct answer is the try-except implementation that catches ZeroDivisionError and returns None. This approach is most Pythonic because it follows the EAFP (Easier to Ask for Forgiveness than Permission) principle, where you attempt the division and handle the exception only if it occurs, rather than checking conditions beforehand with LBYL (Look Before You Leap). On the Certified Associate Python Programmer PCAP exam, this question tests your understanding of exception handling as a core Python idiom, often appearing alongside questions on try-except blocks, built-in exceptions, and the philosophy behind Pythonic code. A common trap is choosing a solution that pre-checks if b equals zero using an if statement—while functional, it is considered less Pythonic because it duplicates the error-checking logic that Python already handles internally. Memory tip: think "try first, ask forgiveness later"—just like borrowing a tool, you use it and apologize only if it breaks, not before.

PCAP Exceptions and File I/O Practice Question

This PCAP practice question tests your understanding of exceptions and file i/o. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 needs to write a function that safely divides two numbers and returns None if division by zero occurs. Which implementation is most Pythonic?

Question 1mediummultiple choice
Study the full Python automation breakdown →

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

def safe_divide(a, b): try: return a/b except ZeroDivisionError: return None

Option A is correct because it uses a try-except block to catch the specific ZeroDivisionError that Python raises when dividing by zero. This is the most Pythonic approach, following the EAFP (Easier to Ask for Forgiveness than Permission) principle, which is preferred over LBYL (Look Before You Leap) in Python. The function returns None only when the exception occurs, preserving the natural behavior of division for all other cases.

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.

  • def safe_divide(a, b): try: return a/b except ZeroDivisionError: return None

    Why this is correct

    Correct: EAFP approach with specific exception.

    Related concept

    Read the scenario before looking for a memorised answer.

  • def safe_divide(a, b): return a/b if b else None

    Why it's wrong here

    LBYL and does not handle ZeroDivisionError properly if b is falsy but non-zero (e.g., 0.0).

  • def safe_divide(a, b): if b != 0: return a/b else: return None

    Why it's wrong here

    LBYL approach, not Pythonic; also does not handle other exceptions like TypeError.

  • def safe_divide(a, b): try: return a/b except ValueError: return None

    Why it's wrong here

    ValueError is not raised by division by zero.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the distinction between EAFP and LBYL, and the trap here is that candidates may choose Option C (LBYL) because it appears safer, or Option D because they confuse ValueError with ZeroDivisionError, not realizing that Python raises a specific exception for division by zero.

Detailed technical explanation

How to think about this question

Under the hood, Python's division operator triggers the __truediv__ method, which raises ZeroDivisionError when the divisor is zero. The EAFP approach is idiomatic in Python because it avoids race conditions in multithreaded code and is often more readable. In real-world scenarios, such as financial calculations or scientific computing, catching the exact exception ensures that other unexpected errors (e.g., TypeError for incompatible types) are not silently masked.

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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

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: def safe_divide(a, b): try: return a/b except ZeroDivisionError: return None — Option A is correct because it uses a try-except block to catch the specific ZeroDivisionError that Python raises when dividing by zero. This is the most Pythonic approach, following the EAFP (Easier to Ask for Forgiveness than Permission) principle, which is preferred over LBYL (Look Before You Leap) in Python. The function returns None only when the exception occurs, preserving the natural behavior of division for all other cases.

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.