Top 30 DevOps Puppet Interview Questions and Answers Pdf
Puppet Interview Questions And Answers for Qualified 2018. Here coding compiler placed usually suggested DevOps puppet interview questions. Certain 30 Puppet Training real-time interview questions are served by the enterprise masters, so this list will accommodate you to solve your next puppet DevOps job interview. All the best for your bright future and sparkling knowledge.
In DevOps Training, Puppet is the most sophisticated and the multiple broadly applied device to Configuration Management. There is a great potentiality that it can be a significant point of controversy in your interview . Therefore here are the collection of commonly asked Puppet interview questions. Curious to grasp further about Puppet check out this Puppet blog series.DevOps Interview Questions. It includes all the DevOps Stages.
1. What is Puppet?
Answer: Puppet Enterprise is a DevOps software platform that is used for automation of infrastructure operations. It runs on Unix as well as on Windows.
We can define system configuration by using Puppet’s language or Ruby DSL.
The system configuration described in Puppet’s language can be distributed to a target system by using REST API calls.
2. What is the architecture of Puppet?
Answer: Puppet is Open Source software. It is based on Client-server architecture. It is a Model-Driven system. The client is also called Agent. And the server is called the Master.
It has the following architectural components:
Configuration Language: Puppet provides a language that is used to configure Resources. We have to specify what Action has to be applied to which Resource. The Action has three items for each Resource: type, title, and list of attributes of a resource. Puppet code is written in Manifests files.
Resource Abstraction: We can create Resource Abstraction in Puppet so that we can configure resources on different platforms. Puppet agent uses a Factor for passing the information of an environment to the Puppet server. In Fact, we have information about IP, hostname, OS etc of the environment.
Transaction: In Puppet, Agent sends Factor to Master server. Master sends back the catalog to Client. The agent applies any configuration changes to the system. Once all changes are applied, the result is sent to Server.
3. What are the main use cases of Puppet Enterprise?
Answer: We can use Puppet Enterprise for the following scenarios:
Node Management: We can manage a large number of nodes with Puppet.
Code Management: With Puppet, we can define Infrastructure as code. We can review, deploy, and test the environment configuration for Development, Testing and Production environments.
Reporting & Visualization: Puppet provides Graphical tools to visualize and see the exact status of infrastructure configuration.
Provisioning Automation: With Puppet, we can automate the deployment and creation of new servers and resources. So users and business can get their infrastructure requirements completed very fast with Puppet.
Orchestration: For a large Cluster of nodes, we can orchestrate the complete process by using Puppet. It can follow the order in which we want to deploy the infrastructure environments.
Automation of Configuration: With Configuration automation, the chances of manual errors are reduced. The process becomes more reliable with this. Learn Devops Training Online From Real-Time Experts
4. What is the Puppet Manifests?
Answer: Every node (or Puppet Agent) has got its configuration details in Puppet Master, written in the native Puppet language. These details are written in the language which Puppet can understand and are termed as Manifests. Manifests are composed of Puppet code and their filenames use the .pp extension.
Now give an example, you can write a manifest in Puppet Master that creates a file and installs apache on all Puppet Agents (Slaves) connected to the Puppet Master.
5. What is Module and How it is different from Manifest?
Answer: Whatever the manifests we defined in modules, can call or include into other manifests. Which makes easier management of Manifests. It helps you to push specific manifests on a specific Node or Agent.
6. What is Factor?
Answer: Sometimes you need to write manifests on conditional expression based on agent-specific data which is available through Factor. Factor provides information like Kernel version, Dist release, IP Address, CPU info, etc. You can define your factor also.
7. What is the use of etckeeper-commit-post and etckeeper-commit-pre on Puppet Agent?
Answer: etckeeper-commit-post: In this configuration file you can define command and scripts which execute after pushing configuration on Agente
etckeeper-commit-pre: In this configuration file you can define command and scripts which execute before pushing configuration on Agent
8. What is Puppet Kick?
Answer: By default Puppet Agent request to Puppet Master after a periodic time which was known as “run interval”. Puppet Kick is a utility which allows you to trigger Puppet Agent from Puppet Master.
9. What is MCollective?
Answer: MCollective is a powerful orchestration framework. Run actions on thousands of servers simultaneously, using existing plugins or writing your own.
10. What’s special about Puppet’s model-driven design
Answer: Traditionally, managing the configurations of a large group of computers has meant a series of imperative steps; in its rawest state, SSH and a for a loop. This general approach grew more sophisticated over time, but it retained the more profound limitations at its root.
Puppet takes a different approach, which is to model everything — the current state of the node, the desired configuration state, the actions taken during configuration enforcement — as data: each node receives a catalog of resources and relationships, compares it to the current system state, and makes changes as needed to bring the system into compliance.
The benefits go far beyond just healing the headaches of configuration drift and unknown system state: modeling systems as data let Puppet simulate configuration changes, track the history of a (sap training) system over its lifecycle, and prove that refactored manifest code still produces the same system state. It also drastically lowers the barrier to entry for hacking and extending Puppet: instead of analyzing code and reverse-engineering the effects of each step, a user can just parse data, and sysadmins have been able to add significant value to their Puppet deployments with an afternoon’s worth of Perl scripting.
11. Why does Puppet have its language? Why not use XML or YAML as the configuration format? Why not use Ruby as the input language
Answer: The language used for manifests is ultimately Puppet’s human interface, and XML and YAML, being data formats developed around the processing capabilities of computers, are horrible human interfaces. While some people are comfortable reading and writing them, there’s a reason why we use web browsers instead of just reading the HTML directly. Also, using XML or YAML would limit any assurance that the interface was declarative — one process might treat an XML configuration differently from another.
12. Can Puppet manage workstations?
Answer: Yes, Puppet can manage any machine and is used to manage many organizations that have a mix of laptops and desktops.
13. Does Puppet run on Windows?
Answer: Yes. As of Puppet 2.7.6 basic types and providers do run on Windows, and the test suite is being run on Windows to ensure future compatibility. More information can be found on the Puppet on Windows page, and bug reports and patches are welcome.
14. What size organizations should use Puppet?
Answer: There is no minimum or maximum organization size that can benefit from Puppet, but there are sizes that are more likely to benefit. Organizations with only a handful of servers are unlikely to consider maintaining those servers to be a real problem, while those that have more need to consider carefully how they eliminate manual management tasks.
15. My servers are all unique; can Puppet still help?
All servers are at least somewhat unique, but very few servers are unique; hostnames and IP addresses (e.g.) will always differ, but nearly every server runs a relatively standard operating system. Servers are also often very similar to other servers within a single organization — all Solaris servers might have similar security settings, or all web servers might have roughly equivalent configurations — even if they’re very different from servers in other organizations. Finally, servers are often needlessly unique, in that they have been built and managed manually with no attempt at retaining appropriate consistency.
Puppet can help both on the side of consistency and uniqueness. Puppet can be used to express the consistency that should exist, even if that consistency spans arbitrary sets of servers based on any data like operating system, data center, or physical location. Puppet can also be used to handle uniqueness, either by allowing the special provision of what makes a given host unique or through specifying exceptions to otherwise standard classes.
16. Who is Puppet Labs?
Answer: Puppet Labs (formerly Reductive Labs) is a small, private company focused on re-framing the server automation problem.
17. How should I upgrade Puppet and Factor?
Answer: The best way to install and upgrade Puppet and Factor is via your operating system’s package management system, using either your vendor’s repository or one of Puppet Labs’ public repositories.
If you have installed Puppet from source, make sure you remove old versions entirely (including all application and library files) before upgrading. Configuration data (usually located in/etc/puppet or /var/lib/puppet, although the location can vary) can be left in place between installs.
18. What characters are permitted in a class name? In a module name? In other identifiers?
Answer: Class names can contain lowercase letters, numbers, and underscores, and should begin with a lowercase letter. can be used as a namespace separator.
The same rules should be used when naming defined resource types, modules, and parameters, although modules and parameters cannot use the namespace separator.
Variable names can include alphanumeric characters and underscore, and are case-sensitive.
19. How do I document my manifests?
Answer: The puppet language includes a simple documentation syntax, which is currently documented on the Puppet Manifest Documentation wiki page. The puppet doc command uses this inline documentation to automatically generate RDoc or HTML documents for your manifests and modules.
20. How do I manage passwords on Red Hat Enterprise Linux, CentOS, and Fedora Core?
Answer: As described in the Type reference, you need the Shadow Password Library, which is provided by the ruby-shadow package. The ruby-shadow library is available natively for fc6 (and higher) and should build on the corresponding RHEL and CentOS variants.
21. How do all of these variables, like $operatingsystem, get set?
Answer: The variables are all set by Factor. You can get a full listing of the available variables and their values by running factor by itself in a shell.
22. What is Puppet Module and How it is different from Puppet Manifest?
Answer: A Puppet Module is a collection of Manifests and data (such as facts, files, and templates), and they have a specific directory structure. Modules are useful for organizing your Puppet code because they allow you to split your code into multiple Manifests. It is considered the best practice to use Modules to organize almost all of your Puppet Manifests.
Puppet programs are called Manifests. Manifests are composed of Puppet code and their file names use the .pp extension.
23. What happens if I am on Puppet 2.6x or earlier?
Answer: Nothing changes for you. Puppet 2.6.x remains licensed as GPLv2. The license change is not retroactive.
24. Does this change affect all the components of a Puppet?
Answer: As part of this change, we’re also changing the license of the Factor system inventory tool to Apache. This change will take effect with Factor version 1.6.0, and earlier versions of Factor will remain licensed under the GPLv2 license. This change will bring the licensing of Puppet’s two key components into alignment.
25. What is Puppet Catalog?
Answer: When configuring a node, the Puppet Agent uses a document called a catalog, which it downloads from a Puppet Master. The catalog describes the desired state for each resource that should be managed and may specify dependency (pivotal training) information for resources that should be managed in a certain order.
If your interviewer wants to know more about it mention the below points:
Puppet compiles a catalog using three main sources of configuration info:
- Agent-provided data
- External data
- Puppet manifests
26. What are the Commands to sign Requested Certificates?
puppet –sign hostname-of-agent (2.6)
puppet ca sign hostname-of-agent (3.0) Devops Online Training
27. What does this mean if I or my company have or want to contribute code to Puppet?
Answer: As part of this license change, Puppet Labs has approached every existing contributor to the project and asked them to sign a Contributor License Agreement or CLA.
Signing this CLA for yourself or your company provides both you and Puppet Labs with additional legal protections and confirms:
1. That you own and are entitled to the code you are contributing to Puppet
2. That you are willing to have it used in distributions
This gives assurance that the origins and ownership of the code cannot be disputed in the event of any legal challenge.
28. What if I haven’t signed a CLA?
Answer: If you haven’t signed a CLA, then we can’t yet accept your code contribution into Puppet or Factor. Signing a CLA is very easy: simply log into your GitHub account and go to our CLA page to sign the agreement.
We’ve worked hard to try to find to everyone who has contributed code to Puppet, but if you have questions or concerns about a previous contribution you’ve made to Puppet and you don’t believe you’ve signed a CLA, please sign a CLA or contact us for further information.
29. Does signing a CLA change who owns Puppet?
Answer: The change in license and the requirement for a CLA doesn’t change who owns the code. This is a pure license agreement and NOT a Copyright assignment. If you sign a CLA, you maintain full copyright to your code and are merely providing a license to Puppet Labs to use your code.
All other code remains the copyright of Puppet Labs.
30. Which versions of Ruby does Puppet support?
Answer: Puppet requires an MRI Ruby interpreter. Certain versions of Ruby are tested more thoroughly with Puppet than others, and some versions are not tested at all. Run ruby –version to check the version of Ruby on your system.
Starting with Puppet 4, puppet-agent packages do not rely on the OS’s Ruby version, as it bundles its own Ruby environment. You can install puppet-agent alongside any version of Ruby or on systems without Ruby installed. Likewise, Puppet Enterprise does not rely on the OS’s Ruby version, as it bundles its own Ruby environment. You can install PE alongside any version of Ruby or on systems without Ruby installed. The Windows installers provided by Puppet Labs don’t rely on the OS’s Ruby version and can be installed alongside any version of Ruby or on systems without Ruby installed. Devops Video Training.
All Devops Interview Questions
Devops VideosDuration: 25+ Hours
Free Bundle Access
Course Future Updates