Task 7.1: Understand how to operate HCP Terraform

• AHealth assessments are a Premium feature whatever the execution mode, unavailable on Standard

  Incorrect

  Health assessments are available in the Standard and Premium editions.

• BContinuous validation needs check blocks, and without them drift detection is skipped as well

  Incorrect

  Drift detection runs regardless of check blocks; continuous validation simply has fewer conditions to evaluate.

• CAssessments require remote or agent execution mode, which these runs do not use

  Correct

  Workspaces need remote or agent execution mode for health assessments, because HCP Terraform runs a speculative plan to assess them.

• DTerraform 1.15 is newer than health assessments support; pin 1.3

  Incorrect

  Drift detection needs 0.15.4 or later and continuous validation 1.3 or later; newer versions qualify.

Health assessments need Standard or Premium, a supported Terraform version, remote or agent execution and a successful latest run. Local execution mode keeps state in HCP Terraform but runs nothing there.

• AIt is canceled, and the next one waits for the next period

  Correct

  A new run cancels the current assessment, and HCP Terraform runs the next assessment during the next assessment period.

• BThe new run waits until the assessment ends

  Incorrect

  The run goes ahead, and the assessment in progress is canceled.

• CBoth run at once against the same state

  Incorrect

  The assessment is canceled instead.

• DThe assessment restarts as soon as the run finishes

  Incorrect

  It waits for the next scheduled period.

Workspaces with very frequent runs may rarely complete an assessment for this reason.

• AAny user with plan permission can start one from the CLI

  Incorrect

  On-demand assessments are only in the UI and need workspace admin.

• BSeveral can run at once to speed things up

  Incorrect

  Another assessment cannot start while one is in progress.

• CIt is UI-only and resets the automated schedule

  Correct

  On-demand assessments are only available in the UI, and each one resets the scheduling for automated assessments.

• DIt runs the next apply automatically if drift is found

  Incorrect

  Assessments report drift; they do not apply changes.

Use Start health assessment on the workspace's Health page.

• ATwelve workspaces with auto-apply

  Incorrect

  Auto-apply is not deployment group orchestration.

• BOne workspace with twelve variable sets

  Incorrect

  One workspace holds one state.

• CRun triggers between regional deployment workspaces

  Incorrect

  Run triggers chain runs; they do not approve groups.

• DA Stack with deployment groups

  Correct

  Deployment group orchestration rules are supported by Stacks and not by workspaces.

Workspaces keep features Stacks lack, such as continuous validation, so compare the feature table before choosing.

• AAs a zip archive of the parent folder

  Incorrect

  The API requires a tar.gz with the configuration at its root.

• BAs a tar.gz whose root holds the .tf files

  Correct

  The upload must be a tar.gz, and extracting it must give paths like ./main.tf with no intermediate directories.

• CAs a git bundle of the whole repository

  Incorrect

  This workflow does not fetch from version control.

• DAs one JSON document holding all .tf contents

  Incorrect

  The API expects an archive of files.

Create a configuration version first to get the upload URL; the token needs queue plans permission on the workspace.