BC for sure

You should create the equivalent configuration first, and then run import to load it on the state file.

there is no 'import-gcp' in terraform official doc

there is no 'import-gcp' in terraform official doc

BCBCBCBCBCBC

There are two ways to manage existing resource using Terraform You can use 'terraform import' or you can use the import block So answers are: B. Use the terraform import command for the existing VMs Most Voted C. Write Terraform configuration for the existing VMs https://developer.hashicorp.com/terraform/cli/import/usage https://developer.hashicorp.com/terraform/language/import

B. Use the terraform import command for the existing VMs C. Write Terraform configuration for the existing VMs

i choose BC

i choose BC

BC are the correct answers here

Write configuration and import.

B&C are correct

B.True C. True

BC are the correct options: B. Use the terraform import command for the existing VMs. This command allows you to import existing infrastructure into your Terraform state file so that Terraform can manage it. You will need to provide the resource type and name, along with any required attributes, for each VM you want to import. C. Write Terraform configuration for the existing VMs. Once the VMs have been imported into the Terraform state file, you will need to write configuration code that describes the desired state of the VMs. This will typically involve creating a new Terraform module or modifying an existing one to include the imported resources. Option A is incorrect because provisioning new VMs with the same names would create duplicate resources and could cause conflicts with the existing VMs. Option D is also incorrect because there is no terraform import-gcp command in Terraform. The correct command for importing GCP resources is simply terraform import.

BC is correct https://developer.hashicorp.com/terraform/tutorials/state/state-import

B,C - first write the configuration and then import

Write configuration then import the existing infrastructure.