7c Describe When and How to Use Verbose Logging TERRAFORM-ASSOCIATE-004 Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A colleague has set TF_LOG=DEBUG in their shell to troubleshoot an issue. After the issue is resolved, they forget to unset it. What is the most likely consequence of this oversight?

   • AAll subsequent Terraform commands will produce verbose debug output, slowing down execution and cluttering the console.
   • BTerraform will automatically reset TF_LOG after the first command completes.
   • CThe debug logs will be written to a file named 'debug.log' in the current directory.
   • DTerraform will fail to run because DEBUG is not a valid log level.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   In a verbose log, what does the order of log entries typically represent?

   • AThe order of plugins as they were installed.
   • BThe chronological sequence of operations performed by Terraform.
   • CThe order of resource definitions in the configuration file.
   • DA random order that has no meaning.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   You are investigating a Terraform state file that has been corrupted. You need to understand the sequence of operations that led to the corruption. What is the best approach?

   • ARun terraform state list to see the resources in the state file.
   • BEnable TF_LOG=TRACE and TF_LOG_PATH=/tmp/state.log, then re-run the operation that caused the corruption.
   • CEnable TF_LOG=DEBUG and inspect the state file directly.
   • DUse the terraform console to inspect the state.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   By default, where does Terraform write verbose log output when TF_LOG is enabled?

   • ATo the system syslog
   • BTo standard error (stderr)
   • CTo standard output (stdout)
   • DTo a file named terraform.log in the current directory
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   You are troubleshooting a Terraform configuration that fails only when run in a specific CI/CD pipeline. The pipeline runs terraform apply with TF_LOG=TRACE and captures the output. You notice that the log shows a '403 Forbidden' error from the cloud provider, but the same configuration works locally. The pipeline uses a service principal, while your local environment uses your personal credentials. What is the most likely cause of the failure?

   • AThe pipeline is using a different Terraform configuration than your local environment.
   • BThe pipeline is running terraform apply without first running terraform init.
   • CThe service principal lacks the required permissions on the target resource group.
   • DThe pipeline is running an older version of Terraform than your local environment.
   Reveal Solution Discussion Select an answer first