A.True

B.False

A.True

B.False

A.Save a generated execution plan to apply later

B.View the execution plan and check if the changes match your expectations

C.Schedule Terraform to run at a planned time in the future

D.Execute a plan in a different workspace

A.terraform taint module.foo.module.bar.baz

B.terraform taint module.foo.bar.aws_instance.baz

C.terraform taint module.foo.module.bar.aws_instance.baz

D.terraform taint foo.bar.aws_instance.baz

A.the resource is marked as tainted
Explanation
If a resource successfully creates but fails during provisioning, Terraform will error and mark the resource as "tainted". A resource that is tainted has been physically created, but can't be considered safe to use since provisioning failed. Terraform also does not automatically roll back and destroy the resource during the apply when the failure happens, because that would go against the execution plan: the execution plan would've said a resource will be created, but does not say it will ever be deleted.

B.it is automatically deleted

C.the terraform plan is rolled back and all provisioned resources are removed

D.Terraform attempts to provision the resource up to three times before exiting with an error