Question 1

Which approach ensures you can use Hiera data in a class but still allow overrides when calling that class?

Options :

A : Disallow parameter overrides entirely to maintain data purity

B : Mark class parameters with default lookup calls (e.g., lookup('some_key', ...)) but allow external overrides

C : Hardcode all parameters in the class so it’s not parameterized

D : Merge all data into node definitions ignoring the class parameters

Answer: B

Question 2

How might you integrate a “hotfix” for production code that bypasses the usual dev -> test flow while retaining environment isolation?

Options :

A : Hardcode environment merges for that node ignoring standard flow

B : Freeze all code merges until the hotfix is undone

C : Create a dedicated hotfix branch mapped to a hotfix environment or directly patch production if tested quickly but keep the patch in version control for future merges

D : Merge it into dev first so the node sees immediate changes

Answer: C

Question 3

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

Question 4

How might you securely tune Puppet’s configuration to handle multiple agent runs from an SSL standpoint?

Options :

A : Using certificate revocation lists, ensuring only valid agent certs are trusted

B : Disabling SSL entirely to simplify the handshake

C : Relying on environment merges that unify node keys

D : Storing agent keys in a public Git repository for easy distribution

Answer: A

Question 5

Which statement describes a recommended approach to verifying the maintainability of a Puppet Forge module?

Options :

A : Check if the module’s license mentions unlimited usage rights

B : Review the module’s Git repository for recent commits, code quality, and community interaction

C : Focus only on the readme file’s length and the popularity statistics

D : Use the module in a mission-critical system to test response times

Answer: B

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

Buying Options: