7a Import Existing Infrastructure into Your Terraform Workspace TERRAFORM-ASSOCIATE-004 Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A developer is trying to import an existing Azure Storage Account into Terraform. The storage account name is 'mystorageacct2024'. They have the resource block azurerm_storage_account.storage in their configuration. They run the import command and receive the error: 'Error: Invalid address to import: expected a resource address in the format resource_type.name'. What is the most likely cause?

   • AThe user is not authenticated with Azure.
   • BThe resource address was mistyped, e.g., azurerm_storage_account.storage.extra.
   • CThe resource block is missing from the configuration.
   • DThe storage account name is incorrect.
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A team is importing an existing AWS VPC into Terraform. The VPC has a CIDR block of 10.0.0.0/16 and is named 'prod-vpc'. The configuration has a resource block aws_vpc.main with cidr_block = "10.0.0.0/16" and tags = { Name = "prod-vpc" }. After running terraform import aws_vpc.main vpc-0a1b2c3d4e5f67890, they run terraform plan and see that Terraform wants to change the instance tenancy from 'default' to 'dedicated'. The actual VPC has tenancy = 'default'. What is the most likely cause?

   • AThe import command imported the wrong VPC.
   • BThe AWS provider defaults to 'dedicated' for new VPCs.
   • CThe configuration specifies instance_tenancy = "dedicated".
   • DThe VPC has a default tenancy that Terraform cannot read.
   Reveal Solution Discussion Select an answer first
4. 18foundation · medium

   When importing a resource, what should you do if you receive an error that the resource ID cannot be found?

   • AVerify that the resource ID is correct and that the resource exists in the specified provider
   • BRun terraform apply to create the resource
   • CRemove the resource block from the configuration
   • DUse terraform state rm to remove the resource
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A team is importing an existing Azure virtual machine into Terraform. The VM is named 'vm-prod' in the 'prod-rg' resource group. They have a resource block azurerm_virtual_machine.vm in their configuration. They run the import command and it succeeds. However, when they run terraform plan, they see that Terraform wants to change the VM's boot diagnostics settings. The actual VM has boot diagnostics enabled with a storage account 'diagstore'. The configuration does not specify boot diagnostics. What is the most likely cause?

   • AThe configuration does not include a boot_diagnostics block, so Terraform plans to disable it.
   • BThe import command failed to capture the boot diagnostics settings.
   • CThe Azure provider defaults to enabling boot diagnostics.
   • DThe storage account 'diagstore' is not in the same region as the VM.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A company has imported an existing AWS RDS instance into Terraform. The instance has a specific parameter group applied. The configuration for aws_db_instance.db does not specify a parameter group name. After import, terraform plan shows that Terraform wants to modify the parameter group. What should the team do to prevent this change?

   • AIgnore the plan and run terraform apply with -target.
   • BRun terraform apply -auto-approve to accept the change.
   • CRemove the parameter group from the RDS instance in AWS.
   • DAdd the parameter_group_name attribute to the configuration with the actual parameter group name.
   Reveal Solution Discussion Select an answer first