JSON configuration alternative in Terraform - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Configuration

intermediate

Identify the correct JSON equivalent of a Terraform resource block

Given the following Terraform HCL resource block, which JSON configuration correctly represents it?

resource "aws_s3_bucket" "example" {
  bucket = "my-bucket"
  acl    = "private"
}

A

{
  "resource": {
    "aws_s3_bucket": {
      "example": {
        "bucket": "my-bucket",
        "acl": "private"
      }
    }
  }
}

B

{
  "aws_s3_bucket": {
    "example": {
      "bucket": "my-bucket",
      "acl": "private"
    }
  }
}

C

{
  "resource": {
    "aws_s3_bucket": {
      "example": [
        {
          "bucket": "my-bucket",
          "acl": "private"
        }
      ]
    }
  }
}

D

{
  "resource": {
    "aws_s3_bucket": {
      "example": {
        "name": "my-bucket",
        "access_control": "private"
      }
    }
  }
}

💡 Hint

Remember that Terraform JSON uses nested objects under "resource" with resource type and name keys.

Terraform JSON configuration requires a top-level "resource" key, then resource type, then resource name as nested objects. The properties must match the HCL keys exactly.

❓ service_behavior

intermediate

What happens if a required attribute is missing in Terraform JSON config?

If you omit a required attribute like "bucket" in the JSON configuration for an aws_s3_bucket resource, what will Terraform do when you run apply?

A Terraform will create the resource but with empty or null values for missing attributes.

B Terraform will throw a validation error and refuse to apply the configuration.

C Terraform will apply the configuration successfully with default values for missing attributes.

D Terraform will ignore the resource block entirely and continue with other resources.

💡 Hint

Think about how Terraform validates required fields before creating resources.

Terraform validates required attributes before applying. Missing required attributes cause errors and prevent apply.

❓ Architecture

advanced

How to represent multiple resources in Terraform JSON configuration?

You want to define two aws_s3_bucket resources named "bucket1" and "bucket2" in Terraform JSON. Which JSON snippet correctly represents this?

A

{
  "resource": {
    "aws_s3_bucket": {
      "bucket1": {"bucket": "bucket-one", "acl": "private"},
      "bucket2": {"bucket": "bucket-two", "acl": "public-read"}
    }
  }
}

B

{
  "resource": [
    {"aws_s3_bucket": {"bucket1": {"bucket": "bucket-one", "acl": "private"}}},
    {"aws_s3_bucket": {"bucket2": {"bucket": "bucket-two", "acl": "public-read"}}}
  ]
}

C

{
  "resource": {
    "aws_s3_bucket": [
      {"bucket1": {"bucket": "bucket-one", "acl": "private"}},
      {"bucket2": {"bucket": "bucket-two", "acl": "public-read"}}
    ]
  }
}

D

{
  "resource": {
    "aws_s3_bucket": {
      "bucket1": {"bucket": "bucket-one", "acl": "private"}
    },
    "aws_s3_bucket": {
      "bucket2": {"bucket": "bucket-two", "acl": "public-read"}
    }
  }
}

💡 Hint

Remember JSON keys must be unique; multiple resources of the same type are nested under the same resource type key.

Terraform JSON groups multiple resources of the same type under one resource type key with unique resource names as keys.

❓ security

advanced

How to securely manage sensitive variables in Terraform JSON configuration?

You have a sensitive variable like a database password. Which approach is best to avoid exposing it directly in Terraform JSON configuration files?

A Encrypt the password manually and store the encrypted string in the JSON configuration.

B Store the password in a separate JSON file in the same directory and import it.

C Use environment variables or Terraform Cloud workspace variables and reference them in JSON without hardcoding.

D Hardcode the password directly in the JSON configuration under a variable block.

💡 Hint

Think about how Terraform handles sensitive data securely without exposing it in config files.

Terraform recommends using environment variables or remote workspace variables to keep sensitive data out of config files.

🧠 Conceptual

expert

What is the main difference between Terraform HCL and JSON configuration formats?

Which statement best describes the key difference between Terraform's HCL and JSON configuration formats?

A JSON supports dynamic expressions and functions, while HCL does not.

B JSON configuration files are only used for Terraform Cloud and not for local Terraform runs.

C HCL configurations cannot be converted to JSON format.

D HCL supports comments and more readable syntax, while JSON does not support comments and is more verbose.

💡 Hint

Consider readability and syntax features of both formats.

HCL is designed for humans with comments and simpler syntax. JSON is strict, no comments, and more verbose.