Question 1

During code promotion, a single dev environment is used for all feature testing. Developers frequently overwrite each other’s changes. They also see chaotic merges into production. How might subdividing dev environments or employing feature environments reduce collisions and produce a cleaner promotion flow?

Options :

A : Locking production until all dev changes are consolidated, ignoring feature-level differences

B : Forcing environment merges every hour to unify all dev code as soon as possible

C : Creating separate feature branches or dev sub-environments isolates each developer’s changes, merging into a shared staging or main dev environment only after testing

D : A single dev environment is always best, ensuring all dev changes unify quickly

Answer: C

Question 2

A newly published module has a tests/ directory with example usage files. You notice they lack any references to your environment or Hiera data. How should you leverage those .pp test files effectively?

Options :

A : Merge all test code into the module’s init.pp so it runs automatically in every puppet run

B : Run them locally as demonstration scenarios, adjusting them to reflect your environment or Hiera references

C : Delete the tests/ directory to avoid confusion with production code

D : Immediately deploy them in production without modification, as test manifests are always safe

Answer: B

Question 3

The “prod” environment references an old major version of a core module. A dev environment references the latest major version. Some modules in dev depend on that new version, but production needs stability. The business needs a phased approach. Which advanced environment strategy satisfies both dev module dependencies and production stability?

Options :

A : Force an immediate upgrade in production ignoring stability concerns

B : Merge environment data from dev and prod to unify module versions on the fly

C : Lock all environments to the older major version to maintain uniformity

D : Maintain a separate environment (e.g., “pre-prod”) that includes the new module major version for deeper testing. Once validated, merge into production carefully

Answer: D

Question 4

When troubleshooting an undefined variable in a Puppet manifest, which step should be taken first?

Options :

A : Overwrite the variable in the Puppet master’s config file

B : Check that the variable is declared or passed correctly before use

C : Disable all conditional logic to ensure the variable is always set

D : Remove parameter references from the class definition entirely

Answer: B

Question 5

A large manifest uses complex conditionals to manage different node types. After a recent change, all node types start receiving the same resource configuration despite seemingly correct conditions. Which initial diagnostic step helps confirm if the conditional expressions are being evaluated as intended?

Options :

A : Run puppet parser validate and assume no runtime issues will occur

B : Reduce all conditionals to a single if-else statement for easier debugging

C : Disable half the conditionals to isolate which block is interfering with other node types

D : Check debug logs or insert notice() statements to confirm actual variable values and branches

Answer: D

Higher Test Marks with Free Online Puppet-Certified-Professional Exam Practice

Buying Options: