What feature of Terraform Cloud and/or Terraform Enterprise can you publish and maintain a set of custom modules which can be used within your organization?

• A.private module registry
• B.Terraform registry
• C.custom VCS integration
• D.remote runs

Comment: *

Name: *

Email: *

Verification: *

You write a new Terraform configuration and immediately run terraform apply in the CLI using the local backend.
Why will the apply fail?

• A.Terraform needs you to format your code according to best practices first
• B.Terraform requires you to manually run terraform plan first
• C.Terraform needs to install the necessary plugins first
• D.The Terraform CLI needs you to log into Terraform cloud first

Comment: *

Name: *

Email: *

Verification: *

Workspaces in Terraform provides similar functionality in the open-source, Terraform Cloud, and Enterprise versions of Terraform.

• A.True
• B.False

Comment: *

Name: *

Email: *

Verification: *

If a module uses a local variable, you can expose that value with a terraform output.

• A.True
• B.False

Comment: *

Name: *

Email: *

Verification: *

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: *