Local-exec provisioner in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What is the output of this Terraform local-exec provisioner?

Given the following Terraform resource with a local-exec provisioner, what will be printed to the console when the resource is created?

Terraform

resource "null_resource" "example" {
  provisioner "local-exec" {
    command = "echo Hello from Terraform"
  }
}

A Terraform apply fails with syntax error

B Error: command not found

C Hello from Terraform

D No output is printed

💡 Hint

The local-exec provisioner runs commands on the machine where Terraform runs.

The local-exec provisioner runs the specified command locally and prints its output to the console during resource creation.

❓ Configuration

intermediate

Which option correctly runs a shell script using local-exec provisioner?

You want to run a shell script named 'setup.sh' located in the same directory as your Terraform configuration using a local-exec provisioner. Which option correctly specifies the command?

A command = "./setup.sh"

B command = "run setup.sh"

C command = "sh ./setup.sh"

D command = "bash setup.sh"

💡 Hint

Consider how to explicitly run a script with bash.

Using 'bash setup.sh' explicitly runs the script with bash, ensuring compatibility. './setup.sh' requires executable permission and correct shebang. 'sh ./setup.sh' may work but is less explicit. 'run setup.sh' is invalid.

❓ Architecture

advanced

What is a key limitation of using local-exec provisioner in Terraform for cloud resource setup?

Which of the following best describes a limitation when using local-exec provisioner to configure cloud resources?

A It requires the command to be run on the machine where Terraform is executed

B It runs commands on the remote cloud resource directly

C It automatically retries failed commands until success

D It can only run commands written in Python

💡 Hint

Think about where local-exec commands actually run.

Local-exec provisioner runs commands locally on the machine running Terraform, not on remote cloud resources. This can limit its use for configuring remote machines directly.

❓ security

advanced

What is a security risk when using local-exec provisioner with sensitive data?

You use local-exec provisioner to run a command that includes sensitive credentials as part of the command string. What is the main security risk?

A Credentials may be exposed in Terraform logs or process list

B Terraform automatically encrypts all command strings

C Local-exec provisioner prevents any data leakage

D Credentials are stored securely in the cloud provider

💡 Hint

Consider where command strings might be visible during execution.

Commands run by local-exec may appear in logs or system process lists, exposing sensitive data if included directly in the command string.

✅ Best Practice

expert

Which approach best follows Terraform best practices when using local-exec provisioner?

You need to run a local script after creating a resource. Which practice aligns best with Terraform's recommended usage of local-exec provisioner?

A Use local-exec provisioner to run all configuration and deployment scripts regardless of complexity

B Use local-exec provisioner only for simple, non-critical commands and avoid complex scripts

C Avoid local-exec provisioner and run all commands manually outside Terraform

D Embed sensitive credentials directly in local-exec commands for convenience

💡 Hint

Think about maintainability and idempotency in Terraform.

Terraform recommends using local-exec provisioner sparingly for simple tasks. Complex or critical configuration is better handled by dedicated configuration management tools or remote-exec provisioner.