2d TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   When should you use the depends_on meta-argument in a Terraform configuration?

   • AWhen you want to create multiple instances of a resource from a single block.
   • BWhen Terraform cannot automatically infer a dependency between two resources.
   • CWhen you want to ignore changes to a resource attribute after creation.
   • DWhen you want to specify a non-default provider configuration for a resource.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   What is the purpose of the provider meta-argument in a resource block?

   • AIt enables or disables the resource in the configuration.
   • BIt sets the region where the resource should be created.
   • CIt specifies which provider configuration to use for the resource.
   • DIt defines the authentication credentials for the resource.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   You are managing a Terraform configuration that creates an Azure VM. The VM's OS disk is encrypted with a customer-managed key. You need to ensure that if the encryption key is rotated, Terraform does not attempt to replace the VM. Which lifecycle argument should you configure?

   • Adepends_on with the disk_encryption_set_id attribute.
   • Bignore_changes with the disk_encryption_set_id attribute.
   • Cprevent_destroy with the disk_encryption_set_id attribute.
   • Dcreate_before_destroy with the disk_encryption_set_id attribute.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   How do you reference the key of an instance created with for_each?

   • Aeach.key
   • Bcount.index
   • Cfor_each.key
   • Deach.value
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   You are configuring a Terraform module that creates an Azure App Service and a diagnostic setting that sends logs to a Log Analytics Workspace. The diagnostic setting resource references the workspace ID and the App Service ID, but Terraform's dependency graph does not automatically order the creation correctly because the workspace is created in a separate module. The diagnostic setting is failing because the workspace does not exist yet. What should you do?

   • AMove the diagnostic setting into the same module as the workspace so the dependency is inferred automatically.
   • BAdd a depends_on argument to the diagnostic setting resource that references the Log Analytics Workspace resource.
   • CSet the lifecycle create_before_destroy argument on the diagnostic setting.
   • DUse a count meta-argument on the diagnostic setting to force it to wait for the workspace.
   Reveal Solution Discussion Select an answer first