Question 1

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 2

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 3

After puppetserver logs show a successful compilation, PuppetDB logs never record a new catalog for that node. The node’s agent run ends with “Catalog retrieved successfully.” Which next step helps reconcile why PuppetDB didn’t store that catalog?

Options :

A : Validate the puppetserver.conf for storeconfigs or store_report set to true

B : Regenerate all SSL certificates for both master and PuppetDB

C : Execute puppet parser validate on the node’s environment to confirm no environment mismatch

D : Remove the node from PuppetDB, then force a puppet run to re-add the data

Answer: A

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

You want each node to reference only one role, which then includes multiple profiles. How does this approach simplify node classification?

Options :

A : It requires each node to define multiple profiles explicitly, leading to greater node-level detail

B : It allows each node to bypass Hiera lookups for class parameters

C : It merges all environment data into the role class, preventing any layering from Hiera

D : It centralizes node-specific logic in a single role, reducing confusion and classification sprawl

Answer: D

Free Puppet-Certified-Professional Mock Exam – Practice Online Confidently

Buying Options: