Why data sources query existing infrastructure in Terraform - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use data sources in Terraform?

What is the main reason Terraform uses data sources to query existing infrastructure?

A To retrieve information about resources created outside Terraform for use in the current configuration

B To delete resources that are no longer needed

C To create new resources based on existing resource templates

D To automatically update Terraform version to match the infrastructure

💡 Hint

Think about how Terraform can use information from resources it did not create.

Data sources allow Terraform to read information about existing resources, so it can reference them without managing their lifecycle.

❓ service_behavior

intermediate

Effect of data sources on Terraform state

When Terraform uses a data source to query existing infrastructure, what happens to the Terraform state file?

A The state file ignores data source information completely

B The state file deletes the existing resource from the cloud provider

C The state file creates a new resource entry for the data source

D The state file records the data source information but does not manage the resource lifecycle

💡 Hint

Consider how Terraform tracks resources it manages versus resources it only reads.

Data sources add read-only information to the state file without managing or changing the resource lifecycle.

❓ Architecture

advanced

Using data sources to integrate multi-team infrastructure

Your team manages a network infrastructure, and another team manages virtual machines. How can Terraform data sources help your team use the network information without recreating it?

A By deleting the existing network and recreating it within your Terraform configuration

B By querying the existing network resources as data sources, your team can reference network IDs without managing them

C By manually copying network configuration files into your Terraform code

D By importing the network resources into your Terraform state and managing them directly

💡 Hint

Think about how to safely use resources managed by others without conflicts.

Data sources let your team read existing network details to use in your configuration without taking ownership or risking conflicts.

❓ security

advanced

Security considerations when using data sources

What is a key security consideration when Terraform queries existing infrastructure using data sources?

A Disable authentication to speed up data source queries

B Grant Terraform full admin permissions to all resources for flexibility

C Ensure Terraform has read-only permissions to prevent accidental changes to existing resources

D Store sensitive data from data sources in public repositories for easy access

💡 Hint

Think about the principle of least privilege in cloud security.

Granting only read-only permissions to Terraform when using data sources helps prevent unintended changes to existing infrastructure.

✅ Best Practice

expert

Best practice for managing dependencies with data sources

When using Terraform data sources to query existing infrastructure, what is the best practice to ensure reliable and consistent deployments?

A Avoid declaring dependencies and rely on Terraform's automatic ordering

B Explicitly declare dependencies using <code>depends_on</code> to control resource creation order

C Manually run separate Terraform commands for data sources and resources

D Use data sources to create resources dynamically during apply

💡 Hint

Consider how Terraform manages resource creation order and dependencies.

Terraform automatically infers dependencies from configuration references, ensuring data sources are queried before dependent resources are created, avoiding the need for explicit depends_on.