- A
They are automatically created when a directory containing .py files is added to sys.path.
Why wrong: A directory with .py files becomes a regular package if it has __init__.py, otherwise it may be importable but not a namespace package unless all directories with the same name on sys.path are combined.
- B
They are supported in Python 3.3 and later.
Correct. PEP 420 introduced namespace packages in Python 3.3.
- C
They allow a single package to be distributed across multiple directories.
Correct. Namespace packages can be split into multiple directories on sys.path.
- D
They can only contain __init__.py files.
Why wrong: Namespace packages can contain any modules, just like regular packages.
- E
They require an __init__.py file.
Why wrong: Namespace packages explicitly do not have __init__.py.
Quick Answer
The correct answer is that namespace packages allow a single package to be distributed across multiple directories. This is because, as defined in PEP 420 and introduced in Python 3.3, a namespace package is a package composed of portions that can reside in different locations on sys.path, and crucially, it does not require an __init__.py file in its directory. On the Certified Associate Python Programmer PCAP exam, this concept tests your understanding of Python’s import system beyond basic packages; a common trap is assuming every directory on sys.path must contain an __init__.py to be a package, but namespace packages deliberately omit this file to enable logical grouping of subpackages from separate file system locations. Remember: if you see a directory without __init__.py that still acts as a package, think namespace—it’s the “invisible glue” for scattered modules. A helpful memory tip: “No init, no problem—namespace splits the system.”
PCAP Modules and Packages Practice Question
This PCAP practice question tests your understanding of modules and packages. 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 statements about namespace packages are true?
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
They are supported in Python 3.3 and later.
Option B is correct because namespace packages were introduced in Python 3.3 via PEP 420. They allow a package to be split across multiple directories on sys.path without requiring an __init__.py file, enabling logical grouping of subpackages from different locations.
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.
- ✗
They are automatically created when a directory containing .py files is added to sys.path.
Why it's wrong here
A directory with .py files becomes a regular package if it has __init__.py, otherwise it may be importable but not a namespace package unless all directories with the same name on sys.path are combined.
- ✓
They are supported in Python 3.3 and later.
Why this is correct
Correct. PEP 420 introduced namespace packages in Python 3.3.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
They allow a single package to be distributed across multiple directories.
Why this is correct
Correct. Namespace packages can be split into multiple directories on sys.path.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
They can only contain __init__.py files.
Why it's wrong here
Namespace packages can contain any modules, just like regular packages.
- ✗
They require an __init__.py file.
Why it's wrong here
Namespace packages explicitly do not have __init__.py.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Python Institute often tests the misconception that all packages require an __init__.py file, but namespace packages are a deliberate exception introduced in Python 3.3, and candidates may incorrectly assume that any directory with .py files automatically becomes a namespace package.
Detailed technical explanation
How to think about this question
Under the hood, Python's import system uses a finder and loader mechanism; for namespace packages, the 'PathFinder' finds multiple directories contributing to the same dotted path and merges them into a single namespace package object. This is particularly useful in large projects or plugins where different teams maintain separate directory trees that should be importable under a common namespace, such as 'company.product.plugin_a' and 'company.product.plugin_b' residing in different locations on the filesystem.
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.
- →
Modules and Packages — study guide chapter
Learn the concepts, then practise the questions
- →
Modules and Packages 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
Related PCAP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Modules and Packages practice questions
Practise PCAP questions linked to Modules and Packages.
Strings practice questions
Practise PCAP questions linked to Strings.
Object-Oriented Programming practice questions
Practise PCAP questions linked to Object-Oriented Programming.
Exceptions and File I/O practice questions
Practise PCAP questions linked to Exceptions and File I/O.
PCAP fundamentals practice questions
Practise PCAP questions linked to PCAP fundamentals.
PCAP scenario practice questions
Practise PCAP questions linked to PCAP scenario.
PCAP troubleshooting practice questions
Practise PCAP questions linked to PCAP troubleshooting.
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: They are supported in Python 3.3 and later. — Option B is correct because namespace packages were introduced in Python 3.3 via PEP 420. They allow a package to be split across multiple directories on sys.path without requiring an __init__.py file, enabling logical grouping of subpackages from different locations.
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 →
Keep practising
More PCAP practice questions
- Which TWO of the following are valid ways to raise an exception in Python?
- Match each Python operator to its precedence level (1=highest).
- Match each Python module to its purpose.
- Drag and drop the steps to create and activate a virtual environment in Python into the correct order.
- Drag and drop the steps to create a Python package with subpackages into the correct order.
- Drag and drop the steps to handle an exception in Python using try-except-finally into the correct order.
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.