Question 1

After enabling strict validation for agent run reports, some older modules produce invalid data structures in the final summary, crashing the puppetserver. The admin wants strict reporting for new modules but to exempt legacy modules temporarily. Which advanced approach balances new, strict enforcement with a phased legacy migration?

Options :

A : Switch to ephemeral environment merges ignoring old module data entirely

B : Force puppet-lint to fix all legacy modules instantly

C : Use environment-based or module-based configuration that flags certain legacy modules for relaxed validation, while new or updated modules must pass strict checks.

D : Merge environment logs so new modules unify with old code ignoring strict validation

Answer: C

Question 2

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 3

You have multiple roles referencing the same set of profiles. How does this approach impact code duplication and environment complexity?

Options :

A : The approach forces merging node definitions at the site manifest level only

B : Each role must redefine the same classes and resources, increasing duplication

C : All profiles must be fully rewritten for each role, leading to more complex environment merges

D : Roles can be extremely lightweight, mainly calling profiles, reducing duplication while allowing variety in node definitions

Answer: D

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

Why would you store static configuration files in the files/ directory of a Puppet module?

Options :

A : They can be served directly to nodes without modification, simplifying file distribution

B : They allow custom Ruby code execution inside manifest files when referencing them

C : They block other directories from referencing the same file content

D : They become automatically converted into EPP templates by Puppet during compilation

Answer: A