# Chapter 16 Exercises: Strengthen the Decision Package

These exercises extend the guided lab from a starter architecture decision into a defensible technology-selection package. Complete them after the matrix validates successfully.

## Exercise 1: Add a Fourth Option

Add a fourth candidate to `technology_selection_matrix.csv`. Choose a realistic option, such as a cloud-native lakehouse service, a SaaS analytics platform, or a hybrid warehouse-plus-lake architecture. Update `tests/validate_matrix.py` if needed so that it scores the new option. Rerun the validator and explain whether the new option changes the decision.

## Exercise 2: Add Proof-of-Concept Evidence

Select the riskiest assumption in your current recommendation. Examples include dashboard concurrency, incremental refresh latency, governance integration, data export, or monthly cost under bursty workloads. Write a short POC note that states the assumption, test method, result, and decision impact. Link or summarize that note in the ADR.

## Exercise 3: Stress-Test the Weights

Create two alternative weighting profiles: one optimized for fastest time-to-value and one optimized for long-term portability. Compare the winning option under each profile. If the decision changes, explain which business strategy each result supports.

## Exercise 4: Prepare an Architecture Review

Prepare a one-page review brief for an architecture review board. The brief should include the decision statement, context, top three criteria, candidate ranking, largest risks, mitigation plan, and review trigger. The goal is to make the decision understandable to stakeholders who have not read the full matrix.

## Exercise 5: Define an Exception Process

Suppose another team wants to use a different platform for a specialized workload. Define an exception process that lets teams deviate from the standard architecture without creating uncontrolled sprawl. The process should include required evidence, security review, cost review, operational owner, and sunset or review date.