Question 327 of 511
Modules and PackagesmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is that the `add` function is not imported into the `tools` package namespace. This happens because the `from . import calc` statement inside `__init__.py` only binds the name `calc` to the submodule itself, not to its individual functions. When a user writes `import tools` and then tries `tools.add(1,2)`, Python searches the `tools` namespace for `add` directly, but it only finds the `calc` module object—so `add` remains accessible only as `tools.calc.add`. On the PCAP exam, this tests your understanding of how package namespace and submodule imports work, specifically how `__init__.py` controls what is exposed at the package level. A common trap is assuming that importing a module automatically imports all its contents into the parent namespace. Remember: importing a submodule gives you the module, not its members—think of it as bringing in the toolbox, not the tools inside.

PCAP Modules and Packages Practice Question

This PCAP practice question tests your understanding of modules and packages. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 package 'tools' has the structure: tools/__init__.py, tools/calc.py, tools/io.py. In __init__.py, the developer writes: from . import calc. A user tries: import tools; print(tools.add(1,2)). This fails with AttributeError. Why?

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

The add function is not imported into the tools package namespace.

Option A is correct because the `__init__.py` file only imports the `calc` module itself into the `tools` package namespace, not the `add` function. When a user calls `tools.add(1,2)`, Python looks for `add` directly in the `tools` namespace, but it is not there — it is only accessible as `tools.calc.add`. The `from . import calc` statement binds the name `calc` to the module, not its contents.

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.

  • The add function is not imported into the tools package namespace.

    Why this is correct

    The __init__.py imports the calc module, not its functions.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The function add is not defined in calc.py.

    Why it's wrong here

    We assume add is defined.

  • Relative imports are not allowed in __init__.py files.

    Why it's wrong here

    Relative imports are commonly used in __init__.py.

  • The user should use tools.calc.add instead.

    Why it's wrong here

    That is a workaround, but the question asks why the error occurs.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the misconception that importing a submodule automatically makes its contents available at the package level, when in fact only the submodule name is added to the package namespace.

Detailed technical explanation

How to think about this question

When Python imports a package, it executes the `__init__.py` file and binds the resulting module object to the package name. The `from . import calc` statement adds `calc` as an attribute of the `tools` module, but does not automatically expose any of `calc`'s functions. To make `tools.add` work, the developer would need to explicitly import `add` into `__init__.py`, e.g., `from .calc import add`. This is a common pattern for creating a simplified public API that hides internal module structure.

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?

Modules and Packages — This question tests Modules and Packages — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The add function is not imported into the tools package namespace. — Option A is correct because the `__init__.py` file only imports the `calc` module itself into the `tools` package namespace, not the `add` function. When a user calls `tools.add(1,2)`, Python looks for `add` directly in the `tools` namespace, but it is not there — it is only accessible as `tools.calc.add`. The `from . import calc` statement binds the name `calc` to the module, not its contents.

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

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.