A team is refactoring a configuration that creates an EC2 instance and a security group. They want to create a module called `web_server` that includes both resources. The instance needs the security group ID, and the security group needs the VPC ID from the root module. What is the correct module interface design?

Hardcode the VPC ID inside the module and expose the instance ID as an output.

Pass both the VPC ID and the security group ID as input variables.

Expose the security group ID as an output of the module and pass the VPC ID as an input variable.

Expose the VPC ID as an output of the module and pass the security group ID as an input variable.

A module is designed to provision an EC2 instance with a specific AMI and instance type. The team wants to make the module reusable across different environments. Which inputs should be exposed as variables?

No inputs; all values should be hardcoded for simplicity.

`instance_type` only, with `ami` and `subnet_id` hardcoded.

`ami`, `instance_type`, and `subnet_id`.

`ami` and `instance_type` only, with `subnet_id` hardcoded.

A team has moved a resource into a module and added a `moved` block. However, `terraform plan` still shows the resource will be replaced. What is the most likely reason?

The `moved` block is in the wrong module, so it does not apply.

The `moved` block has a syntax error, so Terraform ignores it.

The resource was not actually moved; it was copied, leaving the original in state.

The resource's configuration changed during the move, causing a replacement.

A developer has extracted a database resource into a module called `db`. The root module still references the database address directly as `aws_db_instance.main`. After running `terraform plan`, the plan shows the database will be replaced. What is the correct way to update the reference?

Keep the reference as `aws_db_instance.main` and use `terraform state rm` to remove it.

Update the root module to reference `module.db.aws_db_instance.main` and add a `moved` block.

Use `terraform import` to import the existing resource into the module.

Change the reference to `module.db.output` and run `terraform apply` without a `moved` block.

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 4Objective 4

4d TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 4)

Part of the Create, maintain, and use Terraform modules domain, which makes up ~13% of our current practice bank. HashiCorp does not publish an official question count, but from its 240-minute exam (~95–160 total, ~12–21 in this domain), expect 3–5 from this objective — we provide 24 practice questions to prepare you well beyond it. (estimate)

24questions here

5free pages

5concepts

Questions 16–20

16application · medium
A team is refactoring a configuration that creates an EC2 instance and a security group. They want to create a module called `web_server` that includes both resources. The instance needs the security group ID, and the security group needs the VPC ID from the root module. What is the correct module interface design?
Select an answer first
17application · medium
A module is designed to provision an EC2 instance with a specific AMI and instance type. The team wants to make the module reusable across different environments. Which inputs should be exposed as variables?
Select an answer first
18application · medium
A team has moved a resource into a module and added a `moved` block. However, `terraform plan` still shows the resource will be replaced. What is the most likely reason?
Select an answer first
19application · medium
A developer has extracted a database resource into a module called `db`. The root module still references the database address directly as `aws_db_instance.main`. After running `terraform plan`, the plan shows the database will be replaced. What is the correct way to update the reference?
Select an answer first
20foundation · easy
When grouping related resources from an existing configuration into a module, what should be defined to allow the module to be configured differently for each call?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by HashiCorp. “TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL” is a trademark of its owner, used for identification only.

4d TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 4)

Questions 16–20

A module is designed to provision an EC2 instance with a specific AMI and instance type. The team wants to make the module reusable across different environments. Which inputs should be exposed as variables?

A team has moved a resource into a module and added a `moved` block. However, `terraform plan` still shows the resource will be replaced. What is the most likely reason?

A developer has extracted a database resource into a module called `db`. The root module still references the database address directly as `aws_db_instance.main`. After running `terraform plan`, the plan shows the database will be replaced. What is the correct way to update the reference?

When grouping related resources from an existing configuration into a module, what should be defined to allow the module to be configured differently for each call?

Keep studying — Create, maintain, and use Terraform modules