{"id":427,"date":"2026-10-14T08:11:36","date_gmt":"2026-10-14T08:11:36","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2015\/09\/02\/chef-configuration-management-interview-questions-and-answers-2\/"},"modified":"2026-10-14T08:11:36","modified_gmt":"2026-10-14T08:11:36","slug":"chef-configuration-management-interview-questions-and-answers-2","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/chef-configuration-management-interview-questions-and-answers-2\/","title":{"rendered":"Chef Interview Q&A (Part 2): Resources, Run-Lists, Bootstrap, and Test Kitchen"},"content":{"rendered":"\n

Chef interview rounds usually go beyond definitions and test whether you understand convergence behavior<\/strong>, resource order<\/strong>, and node lifecycle operations<\/strong>. This revised guide turns the original Q&A into a concise field reference for interview prep and real operations work.<\/p>\n\n\n\n

Originally published on 2015-09-02; fully revised and updated.<\/em><\/p>\n\n\n\n

Original source attribution in the post pointed to learn.chef.io<\/a>. Community cookbooks referenced in the material are available through Chef Supermarket<\/a>.<\/p>\n\n\n\n

Core Chef concepts interviewers expect<\/h2>\n\n\n\n
  • Resource:<\/strong> A unit of desired state (for example, a package, service, or file).<\/li>
  • Recipe:<\/strong> An ordered collection of resources that applies configuration policy.<\/li>
  • Cookbook:<\/strong> A package of recipes plus supporting files (templates, attributes, libraries, etc.).<\/li>
  • Node:<\/strong> A managed compute instance (VM, physical host, or container host context).<\/li>
  • Run-list:<\/strong> The ordered list of recipes\/roles a node applies during a Chef run.<\/li><\/ul>\n\n\n\n

    Resource execution order and default actions<\/h2>\n\n\n\n

    Chef processes resources in the order they appear in a recipe. That ordering can be the difference between a successful converge and a failed run.<\/p>\n\n\n\n

    Default action behavior<\/h3>\n\n\n\n

    If you omit an explicit action<\/code>, Chef uses that resource type\u2019s default action. For example, package resources typically default to install behavior.<\/p>\n\n\n

    package 'httpd'<\/span>\n# No action specified; package resource uses its default action.<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Order-sensitive versus order-insensitive cases<\/h3>\n\n\n
    # Works in expected sequence: package first, service second<\/span>\npackage 'httpd'<\/span>\n\nservice 'httpd'<\/span> do<\/span>\n  action [:enable, :start]\nend<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n
    # Risky sequence: service before package<\/span>\nservice 'httpd'<\/span> do<\/span>\n  action [:enable, :start]\nend\n\npackage 'httpd'<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Comparison<\/th>Equivalent?<\/th>Why<\/th><\/tr><\/thead>
    package<\/code> then service<\/code> vs service<\/code> then package<\/code><\/td>No<\/td>Chef executes top-to-bottom; service actions may fail if package\/service unit is not present yet.<\/td><\/tr>
    action [:enable, :start]<\/code> vs action [:start, :enable]<\/code><\/td>Not strictly<\/td>Both can reach similar end state, but operation order differs and can matter for notifications\/timing.<\/td><\/tr>
    Same file resource attributes in different order<\/td>Yes<\/td>Attribute line order inside a single resource block is not the key behavior driver in this case.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
    service 'httpd'<\/span> do<\/span>\n  action [:stop, :disable]\nend<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    Recipe, cookbook, and run-list relationships<\/h2>\n\n\n\n
    Interviews often probe whether you can connect authoring to execution: resources live in recipes, recipes are packaged as cookbooks, and run-lists define what each node applies and in what order.<\/p>\n\n\n
    knife node run_list add web1 'recipe[apache::default]'<\/span>\nknife node show web1 -a run_list<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    The original material also highlights two server consumption models: running Chef Server on your own infrastructure or using a hosted offering, and using the Starter Kit credentials to securely connect with knife<\/code>.<\/p>\n\n\n\n
    chef-apply vs chef-client vs knife<\/h2>\n\n\n\n
    Tool<\/th>Best for<\/th>Typical scope<\/th><\/tr><\/thead>
    chef-apply<\/code><\/td>Quick local testing\/learning of a single recipe<\/td>One recipe at a time<\/td><\/tr>
    chef-client<\/code><\/td>Normal node convergence in managed environments<\/td>Applies node run-list (one or more cookbooks\/recipes)<\/td><\/tr>
    knife<\/code><\/td>Workstation-to-server operations<\/td>Bootstrap, upload cookbooks, inspect nodes, remote execution<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
    chef-apply .\/example.rb\nchef-client\nknife node list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Node bootstrap and first converge workflow<\/h2>\n\n\n\n
    \nflowchart TD\n    A[Prepare workstation credentials] --> B[Run knife bootstrap]\n    B --> C[Node installs chef-client]\n    C --> D[Node registers with Chef Server]\n    D --> E[Node pulls assigned run-list]\n    E --> F[Chef Infra Client converges resources]\n    F --> G{Configuration drift remains}\n    G -- yes --> H[Update cookbook and upload]\n    H --> F\n    G -- no --> I[Node stays in desired state]\n<\/pre>\n\n\n
    knife bootstrap NODE_IP \\\n  -x USER \\\n  -P 'PASSWORD'<\/span> \\\n  --sudo \\\n  --node-name web1 \\\n  --run-list<\/span> 'recipe[apache::default]'<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Uploading and applying cookbook updates<\/h2>\n\n\n\n
    After editing a cookbook, upload it to Chef Server and trigger a converge on target nodes.<\/p>\n\n\n
    knife cookbook upload awesome_customers\nknife ssh 'name:web1'<\/span> 'sudo chef-client'<\/span>\nssh user@web1.example.com 'sudo chef-client'<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    The source also references Semantic Versioning guidance: setting cookbook version 1.0.0<\/code> once it is considered production-ready.<\/p>\n\n\n\n
    Template example: render node data into an HTML page<\/h2>\n\n\n\n
    This ERB example from the original content demonstrates using node attributes in a template:<\/p>\n\n\n
    <html<\/span>><\/span>\n<body<\/span>><\/span>\n<h1<\/span>><\/span>hello from <%=<\/span> node<\/span>['fqdn<\/span>'] %><\/span><\/h1<\/span>><\/span>\n\n<pre<\/span>><\/span>\n<%=<\/span> node<\/span>['hostname<\/span>'] %><\/span>\n<%=<\/span> node<\/span>['platform<\/span>'] %><\/span> - <%=<\/span> node<\/span>['platform_version<\/span>'] %><\/span>\n<%=<\/span> node<\/span>['memory<\/span>']['total<\/span>'] %><\/span> RAM\n<%=<\/span> node<\/span>['cpu<\/span>']['total<\/span>'] %><\/span> CPUs\n<\/pre<\/span>><\/span>\n<\/body<\/span>><\/span>\n<\/html<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    Then upload the cookbook and run chef-client<\/code> on the node to apply the updated template.<\/p>\n\n\n\n
    Local cookbook testing with Test Kitchen<\/h2>\n\n\n\n
    For faster development cycles, Test Kitchen can create ephemeral instances, converge cookbooks, and tear instances down after validation.<\/p>\n\n\n\n
    Component<\/th>Role<\/th>How it fits the workflow<\/th><\/tr><\/thead>
    Test Kitchen<\/td>Test orchestrator<\/td>Defines platform\/suite matrix and runs converge\/verify lifecycle.<\/td><\/tr>
    Vagrant<\/td>Environment manager<\/td>Bridges Kitchen and local providers; handles VM definitions and lifecycle commands.<\/td><\/tr>
    VirtualBox<\/td>Virtualization provider<\/td>Runs the actual local virtual machines used by Kitchen in this setup.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
    ---<\/span>\ndriver<\/span>:\n  name<\/span>: vagrant<\/span>\n\nprovisioner<\/span>:\n  name<\/span>: chef_zero<\/span>\n\nplatforms<\/span>:\n  -<\/span> name<\/span>: centos-6<\/span>.6<\/span>\n  -<\/span> name<\/span>: centos-6<\/span>.5<\/span>\n\nsuites<\/span>:\n  -<\/span> name<\/span>: default<\/span>\n    run_list<\/span>:\n      -<\/span> recipe<\/span>[motd::default]<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n
    kitchen list<\/span>\nkitchen converge\nkitchen login default<\/span>-centos-66<\/span>\nkitchen login default<\/span>-centos-65<\/span>\nkitchen destroy<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Best practices and common pitfalls<\/h2>\n\n\n\n
    • Explain resource order<\/strong> clearly in interviews; it is one of the most common failure patterns.<\/li>
    • Use run-lists intentionally<\/strong>; sequence across cookbooks can affect service readiness.<\/li>
    • Test cookbook changes in ephemeral environments<\/strong> before production convergence.<\/li>
    • Keep cookbook versions meaningful and increment with change impact.<\/li>
    • Do not assume old platform examples (for example, CentOS 6.x) are suitable for current production baselines.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
      A practical rewrite of classic Chef interview questions, focused on how Chef resources converge, how run-lists drive node configuration, and how to test cookbooks safely. Includes command examples, workflow diagrams, and comparison tables.<\/p>\n","protected":false},"author":1,"featured_media":3372,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[52],"tags":[641,647,407,1523,1518,1520,1519,282,1517,766,507,1521,244,482,637,1522],"class_list":["post-427","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interview-questions-answers","tag-answers","tag-best","tag-chef","tag-chef-configuration-management-interview","tag-chef-interview","tag-chef-interview-qa","tag-chef-interview-questions-and-answers","tag-configuration","tag-configuration-management","tag-interview","tag-list","tag-list-of-chef-interview-questions-and-answers","tag-management","tag-questions","tag-top","tag-top-chef-interview-questions-and-answers"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/427","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=427"}],"version-history":[{"count":5,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/427\/revisions"}],"predecessor-version":[{"id":79301,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/427\/revisions\/79301"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/3372"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=427"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=427"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=427"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}