QUESTION: 233

From the answers below, select the advantages of using Infrastructure as Code.

Provide a codified workflow to develop customer-facing applications.
Safely test modifications using a "dry run" before applying any actual changes.
Easily integrate with application workflows (GitLab Actions, Azure DevOps, CI/CD tools).
Easily change and update existing infrastructure.
Provide reusable modules for easy sharing and collaboration.

Answer(s): B,C,D,E

Explanation:

Infrastructure as Code is not used to develop applications, but it can be used to help deploy or provision those applications to a public cloud provider or on-premises infrastructure.
All of the others are benefits to using Infrastructure as Code over the traditional way of managing infrastructure, regardless if it's public cloud or on-premises.

Reveal Solution Next Question

QUESTION: 234

What resource dependency information is stored in Terraform's state?

Only implicit dependencies are stored in state.
Both implicit and explicit dependencies are stored in state.
Only explicit dependencies are stored in state.
No dependency information is stored in state.

Answer(s): B

Explanation:

Terraform state captures all dependency information, both implicit and explicit. One purpose for state is to determine the proper order to destroy resources. When resources are created all of their dependency information is stored in the state. If you destroy a resource with dependencies, Terraform can still determine the correct destroy order for all other resources because the dependencies are stored in the state.

Reference:

https://www.terraform.io/docs/state/purpose.html#metadata

Reveal Solution Next Question

QUESTION: 235

Consider the following Terraform 0.12 configuration snippet:
1. variable "vpc_cidrs" {
2. type = map
3. default = {
4. us-east-1 = "10.0.0.0/16"
5. us-east-2 = "10.1.0.0/16"
6. us-west-1 = "10.2.0.0/16"
7. us-west-2 = "10.3.0.0/16"
8. }
9. }
10.
11. resource "aws_vpc" "shared" {
12. cidr_block =
13. }
How would you define the cidr_block for us-east-1 in the aws_vpc resource using a variable?

var.vpc_cidrs.0
vpc_cidrs[“us-east-1”]
var.vpc_cidrs[“us-east-1”]
var.vpc_cidrs[0]

Answer(s): C

Reveal Solution Next Question

QUESTION: 236

Your organization has moved to AWS and has manually deployed infrastructure using the console. Recently, a decision has been made to standardize on Terraform for all deployments moving forward. What can you do to ensure that all existing is managed by Terraform moving forward without interruption to existing services?

Submit a ticket to AWS and ask them to export the state of all existing resources and use terraform import to import them into the state file.
Delete the existing resources and recreate them using new a Terraform configuration so Terraform can manage them moving forward.
Resources that are manually deployed in the AWS console cannot be imported by Terraform.
Using terraform import, import the existing infrastructure into your Terraform state.

Answer(s): D

Explanation:

Terraform is able to import existing infrastructure. This allows us take resources we've created by some other means (i.e. via console) and bring it under Terraform management.
This is a great way to slowly transition infrastructure to Terraform.
The terraform import command is used to import existing infrastructure.
To import a resource, first write a resource block for it in our configuration, establishing the name by which it will be known to Terraform.
Example:
resource "aws_instance" "import_example" {

# ...instance configuration...
}
Now terraform import can be run to attach an existing instance to this resource configuration.
$ terraform import aws_instance.import_example i-03efafa258104165f aws_instance.import_example: Importing from ID "i-03efafa258104165f"... aws_instance.import_example: Import complete!
Imported aws_instance (ID: i-03efafa258104165f) aws_instance.import_example: Refreshing state... (ID: i-03efafa258104165f) Import successful!
The resources that were imported are shown above. These resources are now in your Terraform state and will henceforth be managed by Terraform.
This command locates the AWS instance with ID i-03efafa258104165f (which has been created outside Terraform) and attaches its existing settings, as described by the EC2 API, to the name aws_instance.import_example in the Terraform state.

Reveal Solution Next Question

Free Terraform Associate Exam Braindumps (page: 59)

QUESTION: 233

Explanation:

QUESTION: 234

Explanation:

Reference:

QUESTION: 235

QUESTION: 236

Explanation: