Which statement describes a Terraform module?

Which statement describes a Terraform module?

• A. A module is always publicly accessible
• B. A module can only call resources from a single provider
• C. A module is a container for one or more resources
• D. A module cannot call other modules

Answer: (C)

A Terraform module is a container for one or more resources that are managed as a unit. It groups related resources, along with input variables and outputs, into a reusable configuration you can invoke from a root module or other modules. This packaging lets you compose complex infrastructure by reusing and parameterizing common patterns, and you can mix resources from multiple providers inside a single module. You can also have modules call other modules to build layered, modular infrastructure. For example, you might have a module that sets up a network with subnets and security groups, and another module that provisions compute instances and attaches the network; the outer module can pass in region and sizing parameters and receive identifiers like the VPC ID as outputs. This is what makes modules powerful: they encapsulate a set of resources into a reusable, configurable unit. The other statements don’t fit because a module is not necessarily publicly accessible (it can be local or private, and remote modules published to a registry are optional), it can include resources from more than one provider, and it can call other modules to compose complex configurations.

A Terraform module is a container for one or more resources that are managed as a unit. It groups related resources, along with input variables and outputs, into a reusable configuration you can invoke from a root module or other modules. This packaging lets you compose complex infrastructure by reusing and parameterizing common patterns, and you can mix resources from multiple providers inside a single module. You can also have modules call other modules to build layered, modular infrastructure.

For example, you might have a module that sets up a network with subnets and security groups, and another module that provisions compute instances and attaches the network; the outer module can pass in region and sizing parameters and receive identifiers like the VPC ID as outputs. This is what makes modules powerful: they encapsulate a set of resources into a reusable, configurable unit.

The other statements don’t fit because a module is not necessarily publicly accessible (it can be local or private, and remote modules published to a registry are optional), it can include resources from more than one provider, and it can call other modules to compose complex configurations.