Question 1

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 2

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 3

Why is it advisable to include environment-specific Hiera hierarchies for large-scale code usage across dev, test, and prod?

Options :

A : So that all environment data merges into a single universal set of configuration values

B : It merges everything at top scope, ignoring local environment differences

C : It allows each environment to override or provide unique data (credentials, settings) without affecting other environments

D : It prevents environment merges from referencing production code

Answer: C

Question 4

If you notice frequent collisions between two teams’ changes in the same module but different environments, what environment-based best practice could mitigate these collisions?

Options :

A : Force all changes into a single environment to avoid branching errors

B : Disable version control merges for that module, forcing local manual updates

C : Rely on puppet-lint to unify both teams’ changes automatically

D : Each team uses a dedicated dev environment or feature branch for changes, merging them only after they’re tested, preventing direct collisions on the main environment

Answer: D

Question 5

You use puppet apply --noop to preview changes, but it fails with an undefined variable error for a parameter that you know is set in production. Which factor might explain why the variable is missing in a no-op test environment?

Options :

A : The production environment data from Hiera or node classification may not be loaded in a local apply

B : puppet parser validate must be used to load environment variables automatically

C : The variable references a built-in function that’s disabled in no-op mode

D : Variables are only valid if you run in a fully enforced mode

Answer: A

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

Buying Options: