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

A developer wrote a Bolt plan that runs a script installing packages on Debian nodes, then calls an agent-based run. RHEL nodes fail with “package resource undefined” in the plan. They want one plan for both distros. Which technique harmonizes agent-based steps with script-based steps for cross-platform usage?

Options :

A : Merge environment data in puppet.conf so the plan is identical across distros without conditions

B : Create conditional steps in the Bolt plan to run the Debian script only if $facts['os']['name'] is Debian, while RHEL uses an agent-based package resource in that same plan

C : Provide a single universal script for both distros, ignoring the agent run approach

D : Perform all installation using the agent-based run, skipping scripts on both distros

Answer: B

Question 4

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

Question 5

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

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

Buying Options: