Terraform state pull and push - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you run terraform state pull?

You run terraform state pull in your Terraform project directory. What is the output or result of this command?

A It downloads the current remote state file and prints it to your terminal in JSON format.

B It uploads your local state file to the remote backend, overwriting the remote state.

C It deletes the remote state file from the backend storage.

D It initializes the backend configuration and prepares Terraform to work with the remote state.

💡 Hint

Think about what 'pull' means in everyday life, like pulling data down to you.

The terraform state pull command fetches the current remote state file and prints it in JSON format to your terminal. It does not modify or upload any state.

❓ service_behavior

intermediate

What does terraform state push do?

You have a local state file that you want to upload to the remote backend. What does running terraform state push do?

A Uploads the local state file to the remote backend, replacing the existing remote state.

B Downloads the remote state file and merges it with the local state file.

C Deletes the local state file and replaces it with the remote state file.

D Initializes the backend and prepares Terraform to use remote state.

💡 Hint

Think about what 'push' means, like pushing something up or sending it somewhere.

The terraform state push command uploads your local state file to the remote backend, overwriting the remote state file.

❓ Architecture

advanced

Which backend configuration ensures safe state locking when multiple users run Terraform?

You want to configure Terraform to store state remotely and prevent multiple users from overwriting state at the same time. Which backend configuration below achieves this?

A Use the local backend with state files stored on a shared network drive.

B Use the Terraform CLI without any backend configuration.

C Use the S3 backend without any locking mechanism configured.

D Use the S3 backend with DynamoDB table enabled for state locking.

💡 Hint

Think about how to prevent two people from editing the same file at once.

The S3 backend combined with a DynamoDB table provides state locking to prevent concurrent modifications, ensuring safe collaboration.

❓ security

advanced

What is a security risk of manually running terraform state push with a local state file?

You manually run terraform state push to upload a local state file to the remote backend. What is a potential security risk of this action?

A The command automatically encrypts the state file, so there is no security risk.

B You might overwrite the remote state with outdated or incorrect information, causing infrastructure drift.

C It exposes your cloud provider credentials in the state file to the public internet.

D It deletes all resources managed by Terraform without confirmation.

💡 Hint

Think about what happens if you replace the current state with an old version.

Manually pushing a local state file can overwrite the remote state with outdated data, causing Terraform to lose track of real infrastructure changes, which can lead to errors or resource mismanagement.

🧠 Conceptual

expert

After running terraform state pull, you modify the JSON state file locally. What happens if you then run terraform state push with this modified file?

You pulled the remote state with terraform state pull, edited the JSON state file manually, and then pushed it back with terraform state push. What is the expected outcome?

A Terraform merges your changes with the remote state automatically, preserving all existing resources.

B Terraform validates the JSON and rejects the push if any changes are detected.

C The remote state is replaced with your modified state, which may cause Terraform to mismanage resources if the changes are incorrect.

D The push command fails because manual edits to state files are not allowed.

💡 Hint

Consider what happens when you replace a file with a changed version without checks.

Terraform does not validate or merge manual changes to the state file. Pushing a modified state replaces the remote state exactly, which can cause Terraform to lose track of resources or behave unexpectedly if the changes are invalid.