Question 16 of 511
Modules and PackageseasyMultiple SelectObjective-mapped

Quick Answer

The answer is `from mymod import func` and `from mymod import func as myfunc`. Both are valid because when a module resides in the same directory as your script, Python automatically includes that directory in its module search path, so a direct import statement works without any relative prefix like a dot. The `from ... import` syntax specifically pulls the function into the current namespace, and the `as` clause simply renames it locally, which is fully supported. On the PCAP exam, this tests your understanding of Python’s import system and the fact that same-directory modules do not require `sys.path` manipulation or relative imports. A common trap is thinking you need `import mymod.func` or a dot-based relative import for same-directory modules—neither is correct here. Memory tip: if the module is in the same folder, just use `from modulename import functionname`—no dots needed.

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 of the following are valid ways to import a function named 'func' from a module 'mymod' that is in the same directory as the script?

Question 1easymulti select
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

from mymod import func as myfunc

Option A is correct because the syntax `from mymod import func as myfunc` is a valid Python import statement that imports the function `func` from the module `mymod` and binds it to the local name `myfunc`. Since `mymod` is in the same directory as the script, Python's module search path includes that directory, so the import succeeds without needing a relative import prefix.

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.

  • from mymod import func as myfunc

    Why this is correct

    Valid import with alias.

    Related concept

    Read the scenario before looking for a memorised answer.

  • import mymod.func

    Why it's wrong here

    This syntax imports a submodule, not a function.

  • import func from mymod

    Why it's wrong here

    Invalid syntax.

  • from mymod import func

    Why this is correct

    Direct import of function.

    Related concept

    Read the scenario before looking for a memorised answer.

  • from .mymod import func

    Why it's wrong here

    Relative import only works inside a package.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Python Institute often tests the distinction between absolute and relative imports, and the trap here is that candidates mistakenly think a dot prefix (`.mymod`) is always valid for importing from the same directory, but relative imports only work inside a package, not for standalone scripts.

Detailed technical explanation

How to think about this question

Under the hood, Python's import mechanism uses `sys.path` to locate modules; when a script runs directly, the directory containing the script is added to `sys.path[0]`, allowing absolute imports like `from mymod import func` to work. Relative imports (e.g., `from .mymod import func`) rely on the `__package__` attribute and are designed for intra-package references; they fail with `ImportError: attempted relative import with no known parent package` when the script is executed as `__main__`. A real-world scenario where this matters is when refactoring a script into a package: you must change absolute imports to relative imports to avoid name collisions or ambiguous module resolution.

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.

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: from mymod import func as myfunc — Option A is correct because the syntax `from mymod import func as myfunc` is a valid Python import statement that imports the function `func` from the module `mymod` and binds it to the local name `myfunc`. Since `mymod` is in the same directory as the script, Python's module search path includes that directory, so the import succeeds without needing a relative import prefix.

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.