Question 1

Which practice supports multi-environment data separation for node classification?

Options :

A : Disabling external classifiers in favor of a single site manifest

B : Using an environment that bypasses Hiera merges entirely

C : Maintaining environment-specific Hiera hierarchies that override defaults

D : Storing all environment data in a single top-level YAML file only

Answer: C

Question 2

A lead engineer notices repeated changes in the integration logs related to file timestamps, not content changes. The module is otherwise correct. How can you ensure the test suite ignores these harmless diffs while preserving full idempotence checks?

Options :

A : Always delete the file before each run so Puppet must recreate it

B : Remove the file from your module to bypass the logs entirely

C : Turn off all idempotence checks so no change is ever logged

D : Implement a file resource parameter like replace => false or a carefully tuned parameter set so timestamps aren’t updated if content is unchanged

Answer: D

Question 3

The “prod” environment references an old major version of a core module. A dev environment references the latest major version. Some modules in dev depend on that new version, but production needs stability. The business needs a phased approach. Which advanced environment strategy satisfies both dev module dependencies and production stability?

Options :

A : Force an immediate upgrade in production ignoring stability concerns

B : Merge environment data from dev and prod to unify module versions on the fly

C : Lock all environments to the older major version to maintain uniformity

D : Maintain a separate environment (e.g., “pre-prod”) that includes the new module major version for deeper testing. Once validated, merge into production carefully

Answer: D

Question 4

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 5

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

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

Buying Options: