Why is it important to build a Python executable on the same operating system where it will be run?

Because Python source code is compiled to machine code that is OS-specific

Because the executable file extension must match the target OS

Because executables are platform-specific and may not run on other operating systems

Because the executable will be slower if built on a different OS

A developer is troubleshooting a PyInstaller executable that fails to run on a clean Windows VM. The error is 'The code execution cannot proceed because VCRUNTIME140.dll was not found'. The build machine has Visual Studio installed. What is the best fix?

Rebuild the executable with the --onefile option to include the DLL.

Add VCRUNTIME140.dll to the 'hiddenimports' list.

Use cx_Freeze instead of PyInstaller to avoid the dependency.

Install the Visual C++ Redistributable on the target machine or bundle the DLL with the executable.

After building a PyInstaller onefile executable, a user reports that the program crashes immediately with an error about a missing DLL. The build machine works fine. What is the most likely cause?

The executable was built with the wrong architecture (e.g., 32-bit vs 64-bit).

The target machine lacks a required Visual C++ runtime that the Python interpreter or a dependency needs.

The onefile mode extracts to a temporary directory that is not accessible on the target machine.

The script uses a module that is not included in the bundle.

A developer is using PyInstaller to package a script that imports a module only when a certain environment variable is set. The build succeeds, but the executable fails with ImportError when the environment variable is set. What is the most efficient fix?

Use the --additional-hooks-dir option to provide a custom hook for the module.

Change the import to a top-level import.

Set the environment variable during the build process.

Add the module to the 'hiddenimports' list in the spec file.

GIAC Python Coder

Domain 2Objective 1

Creation of Executables GPYC Practice Questions (Page 5)

Part of the Scripting and Automation domain, which makes up ~23% of our current practice bank. GIAC (SANS) does not publish an official question count, but from its 120-minute exam (~50–80 total, ~12–18 in this domain), expect 4–6 from this objective — we provide 35 practice questions to prepare you well beyond it. (estimate)

35questions here

7free pages

7concepts

Questions 21–25

21foundation · easy
Why is it important to build a Python executable on the same operating system where it will be run?
Select an answer first
22expert · hard
A developer is troubleshooting a PyInstaller executable that fails to run on a clean Windows VM. The error is 'The code execution cannot proceed because VCRUNTIME140.dll was not found'. The build machine has Visual Studio installed. What is the best fix?
Select an answer first
23application · medium
After building a PyInstaller onefile executable, a user reports that the program crashes immediately with an error about a missing DLL. The build machine works fine. What is the most likely cause?
Select an answer first
24foundation · easy
Which common packaging error is often caused by a missing module that was not included in the executable?
Select an answer first
25expert · hard
A developer is using PyInstaller to package a script that imports a module only when a certain environment variable is set. The build succeeds, but the executable fails with ImportError when the environment variable is set. What is the most efficient fix?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GPYC

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GIAC (SANS). “GPYC” is a trademark of its owner, used for identification only.