Task 7.2: Use the CLI to inspect state

• Aterraform providers

  Incorrect

  That shows provider requirements.

• Bterraform graph

  Incorrect

  graph prints the dependency graph in DOT format, not a list of state addresses.

• Cterraform state list

  Correct

  state list lists all resources in the state, including resources in modules, optionally filtered by address.

• Dterraform output

  Incorrect

  output prints output values.

state list is the quickest way to get addresses for other commands.

• Aterraform state list 'module.web.aws_instance.app[0]'

  Incorrect

  state list prints matching addresses, not attributes.

• Bterraform show 'module.web.aws_instance.app[0]'

  Incorrect

  show takes a state or plan file path, not a resource address.

• Cterraform output 'module.web.aws_instance.app[0]'

  Incorrect

  output reads output values only.

• Dterraform state show 'module.web.aws_instance.app[0]'

  Correct

  state show displays the attributes of a single resource instance in state.

list finds addresses; show (under state) prints one resource.

• Aterraform show

  Correct

  terraform show provides human-readable output of the current state, or of a plan file.

• Bterraform output

  Incorrect

  output prints the root module's output values, not the resources recorded in state.

• Cterraform graph

  Incorrect

  graph prints the dependency graph, not state.

• Dterraform console

  Incorrect

  console evaluates the expressions you type against the state; it does not print the state as a whole.

terraform show prints the current state, or a saved plan, for people to read.

• A-lock=false

  Incorrect

  That skips the state lock and still moves everything, which is risky if anyone else runs Terraform at the same time.

• B-dry-run

  Correct

  -dry-run reports every resource instance that matches the given address and leaves the state unchanged.

• C-ignore-remote-version

  Incorrect

  That option relates to the HCP Terraform integration and the remote backend; it does not turn the command into a preview.

• D-compact-warnings

  Incorrect

  That is a plan and apply option for shorter warnings; state mv does not accept it.

State subcommands change state immediately, with no plan in between, so a dry run is the way to check what an address matches before committing to it.

• Astate show output never changes, so the script has a bug

  Incorrect

  Human-oriented output can change.

• BIts output is for people; use terraform show -json

  Correct

  state show output is intended for human consumption; extract data for software with JSON outputs.

• CPass -json to state show to get the same text as JSON

  Incorrect

  state show has no -json option documented.

• DUse state list instead, which includes attributes

  Incorrect

  state list prints addresses only.

Parse JSON, not text meant for people.

• ANo; they work only with local state files

  Incorrect

  They work with remote state.

• BOnly state list works with remote state; the other subcommands need local state

  Incorrect

  All subcommands work with remote state.

• CYes, but only after state pull copies the state locally

  Incorrect

  No manual copy is needed.

• DYes; reads and writes just take a network roundtrip

  Correct

  The state subcommands work with remote state just as with local state, though reads and writes take longer.

Backend location does not change how the state CLI is used.

• Aterraform state show, which keeps the state unlocked while it prints

  Incorrect

  state show prints a resource; it does not evaluate expressions.

• Bterraform output, which edits the state

  Incorrect

  output reads output values only.

• Cterraform console, which locks state while open

  Correct

  console evaluates expressions against values saved in state and holds a state lock while open.

• Dterraform validate, which reads state values

  Incorrect

  validate does not read state.

console is for expressions, including references to things in state.