File provisioner in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

File Provisioner Destination Path Behavior

You use a Terraform file provisioner to copy a file to a remote VM. What will happen if the destination path points to a directory that does not exist on the remote machine?

Terraform

provisioner "file" {
  source      = "app.conf"
  destination = "/etc/myapp/config/"
}

A Terraform creates the missing directory path automatically and copies the file inside it.

B Terraform copies the file to the user's home directory instead.

C Terraform copies the file but renames it to the directory name.

D Terraform fails with an error because the destination directory does not exist.

💡 Hint

Think about how file copying works on remote systems when the target folder is missing.

The file provisioner requires the destination directory to exist. It does not create directories automatically. If the directory is missing, Terraform returns an error.

❓ service_behavior

intermediate

File Provisioner Execution Timing

When does the Terraform file provisioner run during the resource lifecycle?

A Before the resource is created.

B After the resource is created and after all other provisioners.

C After the resource is created but before any <code>remote-exec</code> provisioners.

D Only during resource destruction.

💡 Hint

Consider the order of provisioners in Terraform.

The file provisioner runs immediately after the resource is created, before any remote-exec provisioners run. This allows files to be copied before commands execute remotely.

❓ security

advanced

File Provisioner and Sensitive Data Handling

You need to copy a sensitive configuration file containing secrets to a remote server using the Terraform file provisioner. Which approach best protects the sensitive data during provisioning?

A Use the <code>source</code> attribute pointing to a local file and rely on SSH encryption.

B Store the file content in a Terraform variable marked as sensitive and use <code>content</code> attribute in the provisioner.

C Encode the file content in base64 and decode it on the remote server after copying.

D Copy the file normally and delete it immediately after provisioning.

💡 Hint

Think about Terraform's sensitive variable feature and how it prevents data exposure.

Marking the file content as a sensitive variable and using the content attribute avoids storing the file on disk and reduces exposure in logs. SSH encrypts data in transit but does not prevent local exposure.

❓ Architecture

advanced

File Provisioner Usage in Immutable Infrastructure

In an immutable infrastructure approach, which statement about using the Terraform file provisioner is correct?

A File provisioners should be avoided because they modify resources after creation, breaking immutability.

B File provisioners are ideal because they allow dynamic file changes after resource creation.

C File provisioners are required to configure immutable resources during creation.

D File provisioners automatically create new immutable resources when files change.

💡 Hint

Recall what immutable infrastructure means for resource changes.

Immutable infrastructure means resources are replaced rather than modified. Using file provisioners modifies resources after creation, which breaks immutability principles.

🧠 Conceptual

expert

Terraform File Provisioner Behavior on Resource Update

If you update the source file used in a Terraform file provisioner and run terraform apply without changing the resource configuration, what happens?

A Terraform does not detect changes in the source file and does not re-run the provisioner.

B Terraform throws an error about unmanaged file changes.

C Terraform detects the file change and re-runs the provisioner to update the remote file.

D Terraform destroys and recreates the resource to apply the updated file.

💡 Hint

Think about how Terraform tracks changes and what triggers provisioners.

Terraform does not track changes in local files used by the file provisioner. Without resource configuration changes, it does not re-run provisioners or update remote files.