Which of the following commands will launch the Interactive console for Terraform interpolations?

• A.terraform console
• B.terraform cli
• C.terraform
• D.terraform cmdline

Comment: *

Name: *

Email: *

Verification: *

Which of the following is not a valid Terraform collection type?

• A.set
• B.list
• C.map
• D.tree

Comment: *

Name: *

Email: *

Verification: *

1. resource "aws_s3_bucket" "example" {
2. bucket = "my-test-s3-terraform-bucket"
3. ...} resource "aws_iam_role" "test_role" {
4. name = "test_role"
5. ...}
Due to the way that the application code is written, the s3 bucket must be created before the test role is created, otherwise there will be a problem. How can you ensure that?

• A.Add explicit dependency using depends_on . This will ensure the correct order of resource creation.
• B.This will already be taken care of by terraform native implicit dependency. Nothing else needs to be done from your end.
• C.This is not possible to control in terraform . Terraform will take care of it in a native way , and create a dependency graph that is best suited for the parallel resource creation.
• D.Create 2 separate terraform config scripts , and run them one by one , 1 for s3 bucket , and another for IAM role , run the S3 bucket script first.

Comment: *

Name: *

Email: *

Verification: *

Refer below code where pessimistic constraint operator has been used to specify a version of a provider.
terraform { required_providers { aws = "~> 1.1.0" }}
Which of the following options are valid provider versions that satisfy the above constraint. (select two)

• A.1.1.1
• B.1.2.9
• C.1.1.8
• D.1.2.0

Comment: *

Name: *

Email: *

Verification: *

You have multiple developers working on a terraform project (using terraform OSS), and have saved the terraform state in a remote S3 bucket . However ,team is intermittently experiencing inconsistencies in the provisioned infrastructure / failure in the code . You have traced this problem to simultaneous/concurrent runs of terraform apply command for 2/more developers . What can you do to fix this problem?

• A.Use terraform workspaces feature, this will fix this problem by default , as every developer will have their own state file , and terraform will merge them on server side on its own.
• B.Structure your team in such a way that only one individual will run terraform apply , everyone will just make changes and share with him. Then there will be no chance of any inconsistencies.
• C.Stop using remote state , and store the developer tfstate in their own machine . Once a day , all developers should sit together and merge the state files manually , to avoid any inconsistencies.
• D.Enable terraform state locking for the S3 backend using DynamoDB table. This prevents others from acquiring the lock and potentially corrupting your state.

Comment: *

Name: *

Email: *

Verification: *