Refer to the exhibit. You are tasked with deploying FortiGate using Terraform. When you run the terraform version command during the Terraform installation, you get an error message. What could you…

Question

Options

• AYou must move the binary file to the bin directory.
• BYou must reinstall Terraform.
• CYou must change the directory location to the root directory.
• DYou must assign correct permissions to the ec2-user.

• A
  87% (20)
• B
  9% (2)
• C
  4% (1)

Explanation

Option A is correct because a "command not found" error means the shell cannot locate the Terraform binary in any directory listed in the system's $PATH. When you download and extract Terraform, the binary lands in your current working directory, which is not in $PATH by default. Moving it to /usr/local/bin (or another directory already in $PATH) makes it globally accessible so the terraform version command resolves correctly.

Why the distractors are wrong:

• B (reinstall): Reinstalling won't help - the binary already exists and was extracted successfully; the problem is its location, not a corrupt installation.
• C (change to root directory): Changing directories doesn't fix PATH resolution; you'd still get the error unless you used ./terraform explicitly from the exact directory containing the binary.
• D (assign permissions to ec2-user): A permissions issue would produce a "Permission denied" error, not "command not found" - these are two distinct Linux errors with different causes.

Memory tip: Memorize the Linux error distinction - "command not found" = PATH problem (wrong location), "permission denied" = permissions problem (wrong chmod/owner). For Terraform on EC2, the fix is always sudo mv terraform /usr/local/bin/.

No community discussion yet for this question.