Question 1

Why should you define a clear boundary between roles and profiles, rather than mixing both in a single class?

Options :

A : It avoids confusion and fosters maintainability by separating generic configs from node-specific logic

B : It forces consistent naming conventions across environment manifest files

C : It ensures every resource is declared multiple times for robust duplication

D : It merges data from environment variables into a single place without reusability concerns

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 using facts in conditional logic beneficial in Puppet manifests?

Options :

A : It merges all resource definitions into a single global site.pp

B : It bypasses the need to specify parameters in metadata.json

C : It tailors resource declarations to each node’s actual attributes, avoiding manual OS or hardware checks

D : It allows environment locking to a single OS version

Answer: C

Question 4

During code promotion, a single dev environment is used for all feature testing. Developers frequently overwrite each other’s changes. They also see chaotic merges into production. How might subdividing dev environments or employing feature environments reduce collisions and produce a cleaner promotion flow?

Options :

A : Locking production until all dev changes are consolidated, ignoring feature-level differences

B : Forcing environment merges every hour to unify all dev code as soon as possible

C : Creating separate feature branches or dev sub-environments isolates each developer’s changes, merging into a shared staging or main dev environment only after testing

D : A single dev environment is always best, ensuring all dev changes unify quickly

Answer: C

Question 5

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

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

Buying Options: