OpenStack OpenStack Orchestration (Heat)

Question 1

What file format does OpenStack Heat use to define infrastructure templates?

Accepted Answer

YAML or JSON

Answer

XML only

Answer

INI format

Answer

TOML format

Question 2

What is the top-level key required in every Heat Orchestration Template (HOT)?

Accepted Answer

heat_template_version

Answer

template_version

Answer

openstack_version

Answer

stack_version

Question 3

In OpenStack Heat, what is a 'stack'?

Accepted Answer

A collection of OpenStack resources created and managed as a single unit

Answer

A single VM instance

Answer

A network subnet

Answer

A group of users in Keystone

Question 4

Which Heat resource type is used to create a Nova compute instance?

Accepted Answer

OS::Nova::Server

Answer

OS::Compute::Instance

Answer

OS::Nova::Instance

Answer

OS::Heat::Server

Question 5

What is the purpose of the 'parameters' section in a Heat template?

Accepted Answer

To define user-supplied inputs that customize the stack at launch time

Answer

To list all resources in the stack

Answer

To define output values from the stack

Answer

To specify the Heat API endpoint

Question 6

Which Heat function is used to reference another resource within the same template?

Accepted Answer

get_resource

Answer

get_attr

Answer

get_param

Answer

ref_resource

Question 7

What does the Heat 'outputs' section provide?

Accepted Answer

Values returned to the user after a stack is created, such as IP addresses or URLs

Answer

Error messages from failed deployments

Answer

Log files from compute instances

Answer

A list of all available resource types