← All COA Flashcard Decks

OpenStack Heat & Orchestration Flashcards

7 cards from real COA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 OpenStack Heat & Orchestration flashcards as text
  1. What is the primary purpose of OpenStack Heat?

    Answer: To orchestrate composite cloud applications using templates

    Heat is OpenStack's orchestration service that allows users to describe and automate the deployment of composite cloud applications using templates.

  2. Which template format is the native format for OpenStack Heat templates?

    Answer: Heat Orchestration Template (HOT)

    HOT (Heat Orchestration Template) is the native format for Heat, designed specifically for OpenStack and supporting all Heat features.

  3. What is a 'stack' in the context of OpenStack Heat?

    Answer: A collection of resources instantiated from a Heat template

    A Heat stack is the collection of resources (instances, networks, volumes, etc.) that are created and managed together based on a template.

  4. Which top-level section of a HOT template defines the version of the template format?

    Answer: heat_template_version

    The 'heat_template_version' field is mandatory and specifies which version of the HOT format the template conforms to (e.g., 2021-04-16).

  5. In a HOT template, what section is used to declare inputs that can be customized at stack creation time?

    Answer: parameters

    The 'parameters' section defines user-customizable values that are passed into the template when creating or updating a stack.

  6. Which Heat CLI command is used to create a new stack from a template file?

    Answer: openstack stack create

    The modern OpenStack CLI uses 'openstack stack create' to instantiate a new Heat stack from a template.

  7. What does the 'outputs' section of a HOT template provide?

    Answer: Values returned to the user after stack creation, such as IP addresses

    The 'outputs' section defines key-value pairs that are returned to the user after the stack is created, commonly used to expose resource attributes like IP addresses or URLs.