HFCP study plan
HFCP · Give each week a clear focus.
8 weeks · About 7 hours per week
Cloud Computing Fundamentals & Infrastructure as Code with Terraform
Explain the cloud shared responsibility model and map each layer to what the customer configures versus what the provider configures
Compare IaaS, PaaS, and SaaS using at least two concrete examples per model and state which operational tasks shift to the provider
Install Terraform locally and configure a remote backend against an object storage bucket, then verify state locking works by running two applies concurrently
Write a Terraform configuration that provisions one network and one compute instance using variables, outputs, and a provider version constraint
Trace how terraform init, plan, and apply differ in what they read and write, including what the plan file contains
Your checkpoint
A version-controlled Terraform repository that provisions a network plus one instance from variables, stores state remotely with locking enabled, and includes a README documenting each command run
Infrastructure as Code with Terraform
Refactor a flat configuration into modules with defined input variables, outputs, and a pinned source reference
Demonstrate the difference between count and for_each by building a collection of resources and predicting the plan output for each
Use terraform state commands to inspect, move, and remove a resource from state without destroying the real infrastructure
Configure lifecycle rules including create_before_destroy and prevent_destroy, and explain when each prevents an outage
Write a plan that shows a no-op change after a manual drift edit, then reconcile the drift
Your checkpoint
A modular Terraform project with at least two reusable modules, for_each-driven resources, documented lifecycle rules, and a written drift-reconciliation log with the before and after plan summaries
Infrastructure as Code with Terraform & Automation, CI/CD, and Collaboration
Set up a CI pipeline that runs terraform fmt check, validate, and a saved plan on every pull request
Implement a manual approval gate before apply and explain why plan artifacts must be treated as sensitive
Add automated tests for module behavior using a framework such as Terratest or native terraform test, covering at least one success and one failure path
Configure pre-commit hooks that block commits failing fmt or validate
Describe how workspaces or directory separation isolate environments and choose one approach with written justification
Your checkpoint
A working CI pipeline file that runs fmt, validate, plan, and tests on pull requests, gates apply behind approval, and has produced at least one green run and one intentionally failed run
Networking and Security Automation & Service Networking and Service Mesh
Model a network with public and private subnets, route tables, and a NAT path using Terraform, then verify traffic flow
Write security group and network policy rules that follow least privilege and prove a denied connection is actually blocked
Explain how service discovery resolves a service name to healthy instances and contrast client-side with server-side load balancing
Deploy a service mesh sidecar proxy and observe mTLS-encrypted traffic between two services
Define a mesh traffic policy that splits traffic between two service versions and verify the split empirically
Your checkpoint
A reproducible Terraform stack plus a short lab report showing a blocked connection, a successful mTLS handshake between services, and measured results of a version-weighted traffic split
Secrets Management with Vault
Start a Vault dev server, then repeat the setup with a file backend and explain why dev mode is unsuitable outside labs
Compare token, approle, and userpass auth methods and configure one non-root auth method with a least-privilege policy
Write a policy that grants read on one path and denies another, then prove the denial with a CLI request
Enable a KV v2 secrets engine, store a credential, and demonstrate versioning plus soft delete and undelete
Configure a dynamic database credential or cloud credential engine and show that the lease expires and the credential is revoked
Your checkpoint
A Vault lab repository containing policies as code, an auth method configuration, a KV v2 walkthrough with version history, and captured output proving a dynamic credential was revoked at lease expiry
Secrets Management with Vault & HashiCorp Cloud Platform (HCP) Operations
Explain Vault seal and unseal, and contrast Shamir shares with auto-unseal using a cloud KMS
Integrate an application with Vault by injecting a secret at runtime instead of baking it into an image or environment file
Describe the HCP control plane model and distinguish organization, project, and workspace scoping
Create an HCP Terraform workspace, connect it to a VCS repository, and run a remote plan triggered by a commit
Configure a variable set and a sensitive variable in HCP Terraform, and verify the value is masked in run output
Your checkpoint
An HCP Terraform workspace running remote plans from a repository, with a variable set applied to at least two workspaces and a screenshot-free written record of run IDs and outcomes
HashiCorp Cloud Platform (HCP) Operations & Automation, CI/CD, and Collaboration
Implement a policy-as-code check that fails a plan when a resource violates an approved rule
Design a promotion workflow that moves the same artifact from a non-production to a production workspace with approval
Automate Vault secret rotation and wire the rotated credential into an application without downtime
Explain how run triggers, CLI-driven runs, and API-driven runs differ and pick the right one for a scheduled drift check
Document a rollback procedure for a failed apply and rehearse it in a non-production workspace
Your checkpoint
A drift-detection run scheduled or triggered on a schedule, a policy check that has blocked at least one noncompliant plan, and a rehearsal log of a rollback executed in a non-production workspace
Cloud Computing Fundamentals & Networking and Security Automation & Service Networking and Service Mesh
Review missed practice questions by domain and rewrite the underlying concept in your own words for each miss
Re-derive the shared responsibility boundary for a managed Kubernetes service and a managed database
Re-explain mesh mTLS, service identity, and certificate rotation from memory without notes
Complete two timed mixed-domain practice sets and record per-domain accuracy
Build a one-page reference sheet linking Terraform, Vault, and mesh concepts to the operational problem each solves
Your checkpoint
A per-domain accuracy report from two timed practice sets showing improvement over week 1 baseline, plus a one-page cross-domain reference sheet
Milestones
Week 2: Remote state with locking is working and a modular refactor applies cleanly; you can explain the plan output of a for_each change before running it
Week 4: You have demonstrated a blocked network connection and observed mTLS traffic between two services, and can explain the difference between client-side and server-side load balancing
Week 5: A least-privilege Vault policy is enforced in practice and a dynamic credential has been shown to expire and revoke
Week 6: HCP Terraform runs remote plans from VCS and a sensitive variable is masked in output
Week 7: A policy check has blocked a noncompliant plan and a rollback has been rehearsed end to end
Week 8: Timed practice accuracy is above your week 1 baseline in every domain, with the weakest domain identified and a remediation plan written