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

You want to get involved in the development of Terraform. As this is an open source project, you would like to contribute a fix for an open issue of Terraform. What programming language will need to use to write the fix?

• A.It depends on which command issue related to.
• B.Python
• C.Go
• D.Java

Comment: *

Name: *

Email: *

Verification: *

Which of the following is not a benefit of adopting infrastructure as code?

• A.Reusability of code
• B.Automation
• C.Interpolation
• D.Versioning

Comment: *

Name: *

Email: *

Verification: *

A terraform apply can not _________ infrastructure.

• A.provision
• B.change
• C.import
• D.destroy

Comment: *

Name: *

Email: *

Verification: *

If a Terraform creation-time provisioner fails, what will occur by default?

• A.The resource will be destroyed
• B.The resource will be marked as "tainted"
• C.The resource will not be affected, but the provisioner will need to be applied again
• D.Nothing, provisioners will not show errors in the command line

Comment: *

Name: *

Email: *

Verification: *