- Write a cookbook using you can install apache http server in CentOs and Ubuntu, enable the services and start the service.
- Write a recipe using template resources to create a file, but only if an attribute has a specific value.
- Write a recipe to create a file using a string, but not if “/etc/passwd” exists?
- Write a cookbook to unzip a file, and then move a files from one location to another using batch, bash chef resources?
- Create a role and assign any two cookbooks to role and setup a 2 nodes assigned to role and conerse the role.
- Write a cookbook using install version of latest tomcat and deploy jenkins.war files into war.
- Write a 4 cookbooks php, mysql, apache and webapp respectively and map a dependency between them and install a sample web application.
- Write a cookbook to install git, wget, zip in RHEL and Ubuntu.
- Write a cookbook in which create a file using a string, but only if “/etc/passwd” exists
- Write a coobook to run a batch file that unzips and then moves files from one location to another.
Latest posts by scmgalaxy K (see all)
- Use of runtime variables to save into another variable using register in Ansible - September 6, 2018
- Ansible & Ansible Tower Variable Precedence Hierarchy - September 6, 2018
- How to use template in Ansible? - September 6, 2018
This blog is a strong hands-on learning idea because Chef skills improve fastest when you build real cookbooks instead of only reading theory. Writing multiple small cookbooks forces you to practice the core Chef concepts—resources, recipes, attributes, templates, files, packages, services, and idempotency—so your automation becomes reliable and repeatable. It also teaches good structure: using roles/environments, handling different OS versions, managing secrets safely, and writing clear metadata and README files for team use. A smart way to use these cookbook exercises is to add testing from the start (Test Kitchen + InSpec), run your cookbooks in a clean VM/container, and treat each cookbook like a production project with versioning and Git. Overall, this is a practical roadmap for anyone who wants to move from “Chef user” to “Chef developer” with real confidence.