Question 1

A resource fails to apply with “Parameter has no effect” in logs. What does this typically indicate?

Options :

A : The variable is missing from the node’s classification but included in the class definition

B : The parameter is not supported by the specified resource type

C : The parameter is recognized but cannot be validated with puppet parser validate

D : The environment data is overriding a valid parameter

Answer: B

Question 2

Which Puppet Forge metadata element can reveal external modules or libraries you must install for the main module to function?

Options :

A : The requirements or dependencies list in the metadata file

B : The user reviews rating field

C : The module’s tags section providing descriptive keywords

D : The script logs recorded in the module’s readme

Answer: A

Question 3

Which step helps confirm whether an undefined variable error is caused by Hiera’s data hierarchy?

Options :

A : Disable environment merges in Hiera so only the top-level data is used

B : Move the variable from Hiera into node classification statements

C : Manually override the variable in the class definition

D : Temporarily set a default value for the lookup() call and check logs

Answer: D

Question 4

After enabling strict validation for agent run reports, some older modules produce invalid data structures in the final summary, crashing the puppetserver. The admin wants strict reporting for new modules but to exempt legacy modules temporarily. Which advanced approach balances new, strict enforcement with a phased legacy migration?

Options :

A : Switch to ephemeral environment merges ignoring old module data entirely

B : Force puppet-lint to fix all legacy modules instantly

C : Use environment-based or module-based configuration that flags certain legacy modules for relaxed validation, while new or updated modules must pass strict checks.

D : Merge environment logs so new modules unify with old code ignoring strict validation

Answer: C

Question 5

A new compliance rule mandates that two parameters in a shared class cannot be changed outside of code review. How can Puppet enforce these parameter values in code while still allowing Hiera overrides for the rest of the parameters?

Options :

A : Enforce environment variables for all parameters so code review merges them accordingly

B : Remove all parameter references from Hiera and rely on direct site.pp definitions

C : Store all parameters in Hiera but lock the entire file from external changes

D : Mark those two parameters as final in the class definition, passing all others to Hiera

Answer: D

Confidently Practice Online with Free Puppet-Certified-Professional Exam Cram

Buying Options: