COA OpenStack Heat & Orchestration

Question 1

What is the primary purpose of OpenStack Heat?

Accepted Answer

To orchestrate composite cloud applications using templates

Answer

To monitor OpenStack resource usage and generate alerts

Answer

To manage virtual machine snapshots and backups

Answer

To provide DNS resolution for OpenStack instances

Question 2

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

Accepted Answer

Heat Orchestration Template (HOT)

Answer

AWS CloudFormation Template (CFN)

Answer

YAML Ain't Markup Language (YAML-only)

Answer

JavaScript Object Notation (JSON-only)

Question 3

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

Accepted Answer

A collection of resources instantiated from a Heat template

Answer

A group of compute hosts sharing the same hardware

Answer

A network topology connecting multiple tenants

Answer

A queue of pending resource provisioning jobs

Question 4

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

Accepted Answer

heat_template_version

Answer

format_version

Answer

template_version

Answer

openstack_version

Question 5

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

Accepted Answer

parameters

Answer

inputs

Answer

variables

Answer

arguments

Question 6

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

Accepted Answer

openstack stack create

Answer

heat stack-create

Answer

openstack heat deploy

Answer

heat template-apply

Question 7

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

Accepted Answer

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

Answer

Logging destinations for resource events

Answer

Error messages generated during template validation

Answer

Metric data exported to Ceilometer