Task library BIAC Cloud infrastructure · Phased project Reviewable infrastructure plan pipeline A fictional application team manages a small database, cache, and object store. Reviewers struggle to distinguish harmless configuration changes from destructive replacements.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 25h 30m + setup
Suggested stack TypeScript · Terraform plan JSON · Policy fixtures Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BIAC-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice infrastructure risk analysis, plan integrity, and least-privilege change workflows.
What the team gains Give infrastructure reviewers concrete change scope and recovery consequences.
Before you start Author synthetic infrastructure plans and state snapshots; use local files only and no cloud credentials. Delivery agreement Deliver an offline plan-review tool and synthetic workflow; provision nothing externally.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Normalize resource actions and unknown values.
PHASE 2 Surface destructive changes and policy failures.
PHASE 3 Verify freshness, ownership, and recovery information.
Parse plan authority Normalize resource actions and unknown values.
BIAC-101 Entry ticket; project setup still required Estimated field mix
Cloud infrastructure 70% Developer tooling 30% BIAC-102 Depends on BIAC-101 Estimated field mix
Security 60% Cloud infrastructure 40% Review risk Surface destructive changes and policy failures.
BIAC-103 Depends on BIAC-101, BIAC-102 Estimated field mix
Cloud infrastructure 50% Site reliability 50% BIAC-104 Depends on BIAC-102 Estimated field mix
Security 70% Cloud infrastructure 30% BIAC-105 Depends on BIAC-103 Estimated field mix
Site reliability 60% Cloud infrastructure 40% Bind execution intent Verify freshness, ownership, and recovery information.
BIAC-106 Depends on BIAC-104, BIAC-105 Estimated field mix
Cloud infrastructure 50% Security 30% Developer tooling 20% BIAC-107 Depends on BIAC-106 Estimated field mix
Cloud infrastructure 60% Security 40% BIAC-108 Depends on BIAC-103, BIAC-106, BIAC-107 Estimated field mix
Cloud infrastructure 40% System design 30% Site reliability 30% BIAC-109 Depends on BIAC-108 Estimated field mix
Cloud infrastructure 70% Developer tooling 30% BIAC-110 Depends on BIAC-109 Estimated field mix
Security 60% Cloud infrastructure 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.