To import existing resources into Terraform, you need to do two things1:
Write a resource configuration block for each resource, matching the type and name used in your state file.
Run terraform import for each resource, specifying its address and ID. There is no such command as terraform Import-gcp, and provisioning new VMs with the same names will not import them into Terraform.

The terraform import command is not part of any other Terraform workflow. It must be explicitly invoked by the user with the appropriate arguments, such as the resource address and the ID of the existing infrastructure to import. Reference = [Importing Infrastructure]

C (✅Correct)- If changes require aresource replacement(e.g., changing an immutable attribute like instance type), Terraform willdestroy and recreate the resource.
E (✅Correct)- Terraform only appliesthe configuration in the current directory or workspace.
Incorrect Answers:
A: (❌Incorrect)- terraform apply can run without explicitly passing a plan.
B: (❌Incorrect)- terraform applyautomatically refreshes statebefore making changes.
D: (❌Incorrect)- Terraformcan target specific resourcesusing -target.Official Terraform Documentation Reference:terraform apply - HashiCorp Documentation

To tell Terraform to stop managing a specific resource without destroying it, you can use the terraform state rm command. This command will remove the resource from the Terraform state, which means that Terraform will no longer track or update the corresponding remote object. However, the object will still exist in the remote system and you can later use terraform import to start managing it again in a different configuration or workspace. The syntax for this command is terraform state rm <address>, where <address> is the resource address that identifies the resource instance to remove. For example, terraform state rm aws_instance.ubuntu[1] will remove the second instance of the aws_instance resource named ubuntu from the state. Reference = : Command: state rm : Moving Resources

Rationale for Correct Answer (True):
Local values (locals {}) are scoped to a module and are not directly visible outside. To make them available to callers, you must define outputs in the module. Outputs act as the interface for exposing values from a child module to the root module.
Analysis of Incorrect Option:
False: Incorrect, because locals cannot be exposed directly; only via outputs.
Key Concept:
Outputs are the way to expose information outside of a module.
Reference:
Terraform Exam Objective - Interact with Terraform Modules.