Your team has started using terraform OSS in a big way , and now wants to deploy multi region deployments (DR) in aws using the same terraform files . You want to deploy the same infra (VPC,EC2 ...) in both us-east-1 ,and us-west-2 using the same script , and then peer the VPCs across both the regions to enable DR traffic. But , when you run your script , all resources are getting created in only the default provider region. What should you do? Your provider setting is as below -
# The default provider configuration provider "aws" { region = "us-east-1" }

• A.No way to enable this via a single script . Write 2 different scripts with different default providers in the 2 scripts , one for us-east , another for us-west.
• B.Create a list of regions , and then use a for-each to iterate over the regions , and create the same resources ,one after the one , over the loop.
• C.Use provider alias functionality , and add another provider for us-west region . While creating the resources using the tf script , reference the appropriate provider (using the alias).
• D.Manually create the DR region , once the Primary has been created , since you are using terraform OSS , and multi region deployment is only available in Terraform Enterprise.

Comment: *

Name: *

Email: *

Verification: *

When Terraform needs to be installed in a location where it does not have internet access to download the installer and upgrades, the installation is generally known as to be __________.

• A.non-traditional
  Explanation
  A Terraform Enterprise install that is provisioned on a network that does not have Internet access is generally known as an air-gapped install. These types of installs require you to pull updates, providers, etc. from external sources vs. being able to download them directly.
• B.disconnected
• C.a private install
• D.air-gapped

Comment: *

Name: *

Email: *

Verification: *

A Terraform local value can reference other Terraform local values.

• A.True
• B.False

Comment: *

Name: *

Email: *

Verification: *

Terraform providers are always installed from the Internet.

• A.True
• B.False

Comment: *

Name: *

Email: *

Verification: *

By default, provisioners that fail will also cause the Terraform apply itself to error. How can you change this default behavior within a provisioner?

• A.provisioner "local-exec" { on_failure = "next" }
• B.provisioner "local-exec" { when = "failure" terraform apply }
• C.provisioner "local-exec" { on_failure = "continue" }
• D.provisioner "local-exec" { on_failure = continue }

Comment: *

Name: *

Email: *

Verification: *