Question 1

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 2

You see a module on Puppet Forge with a high “quality score” but contradictory user comments mentioning unaddressed bugs. How do you reconcile this discrepancy before deciding to adopt the module?

Options :

A : Investigate the bug reports, check the module’s issue tracker or repo commits for resolution attempts

B : Assume the user comments refer to an old version, and the quality score indicates it’s now fixed

C : Trust the quality score completely because user comments lack official review

D : Avoid the module entirely, because any negative comments mean it’s unsafe

Answer: A

Question 3

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

Question 4

Several masters share a single PuppetDB instance. A spike in fact storage causes massive load on the DB, slowing down all catalog compiles. Investigations show a node group producing exceptionally large fact sets. Which advanced approach curbs DB load without losing crucial data for the rest of the infrastructure?

Options :

A : Configure a fact blacklist or truncation for particularly large facts from those nodes, or use a specialized approach that reduces certain fact payload sizes before storing in PuppetDB

B : Merge environment data so fewer nodes produce facts daily

C : Lower concurrency globally to slow all agents so the DB can handle large facts

D : Convert all large facts to ephemeral environment merges ignoring the DB

Answer: A

Question 5

What does the before => Class['apache'] relationship accomplish in a Puppet manifest?

Options :

A : It merges the resource with the apache class in a single definition

B : It enforces that the resource it’s attached to must be applied before apache class is evaluated

C : It defers the resource application until the agent’s next run

D : It restarts the current resource after apache is started

Answer: B

Free Puppet-Certified-Professional Mock Exam – Practice Online Confidently

Buying Options: