Question 1

What does it mean if the agent logs say “File[‘/etc/ntp.conf’] is in sync” on multiple consecutive runs?

Options :

A : The file path is invalid, so Puppet skipped it

B : The file resource is not being checked for changes anymore

C : The file was never created by Puppet, so it remains synced with the environment

D : The resource is already in the desired state, so no changes are needed

Answer: D

Question 2

A specialized network firewall module appears on Forge with no mention of Windows compatibility, yet you want to manage firewall rules on Windows nodes. The code uses OS-specific providers. Which approach clarifies if Windows support could be added easily?

Options :

A : Rely on the module’s Forge tags alone: if it’s not labeled “windows,” it’s impossible to adapt

B : Deploy it on Windows and see if it errors, ignoring any disclaimers

C : Review the code’s logic for OS detection and see if the existing providers can be extended or replaced

D : Search for user reviews stating Windows usage, ignoring the code’s own disclaimers

Answer: C

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

When you see multiple versions of a module from different authors on Puppet Forge, what factor should primarily drive your choice?

Options :

A : The one recommended in random community forums with no official documentation

B : Which version aligns best with your Puppet version, dependencies, and environment needs

C : The highest version number, guaranteeing the newest features

D : The module with the smallest file size for faster downloads

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