Well Architect Framework Course Questions

Question 1: "Our Chief Security Officer wants us to implement AES-256 encryption for all data at rest, but our lead engineer says it'll add 15% latency overhead and delay our product launch by 6 weeks. How do you frame this decision?"

High-Authority Answer:

This is a pillar collision between Security (encryption-in-transit/at-rest) and Performance (latency) and Team Velocity (launch timeline). Do not pretend there is a "right answer" — there is a business trade-off to be made. Frame it this way:

"Encryption overhead is real, and the 15% latency tax is quantifiable. Our question is: What is the customer value of launching in 6 weeks vs. 12 weeks with strong encryption? If the market window is critical (launch before a competitor), we may delay encryption and implement it post-launch, accepting temporary risk. If our customers are data-sensitive (fintech, healthcare), the encryption delay is unacceptable. If we're building internal tools, the launch timeline wins. This is not a technical question — it's a business prioritization question, and the CSO, CTO, and CPO must decide together."

The impostor syndrome: "I don't know enough about encryption to make this call." The reality: You don't need to. You need to translate technical constraint into business trade-off language so executives can decide.

Question 2: "Our CFO approved a 20% cloud cost reduction initiative. Our infrastructure team says this requires moving to spot instances and reducing our backup redundancy. What are the second-order consequences?"

High-Authority Answer:

Spot instances have a termination risk. AWS can reclaim them with 2 minutes' notice. Reducing backup redundancy means longer Recovery Time Objective (RTO) if a region fails. The hidden costs are:

Operational risk: When a spot instance terminates mid-deployment, on-call engineers must scramble. This increases MTTR and on-call fatigue.

Reliability risk: Losing backup redundancy means a regional failure could result in multi-hour or multi-day recovery, triggering SLA penalties and customer churn.

Hidden cost: The "savings" of 20% ($X) may be offset by:

SLA penalties for missed uptime targets ($ of lost revenue)

On-call overtime and engineer burnout (turnover cost)

Customer churn from service degradation (lifetime value loss)

"The 20% cost reduction is real, but the residual risk is higher. We should model the probability of spot terminations and regional failures, then calculate expected financial impact. If the risk-adjusted cost of SLA breaches exceeds the $X savings, we should reject this initiative."

The impostor syndrome: "I'm not qualified to make CFO-level financial arguments." The reality: You are translating risk into language the CFO understands (expected value, SLA penalties, customer churn). That's your job as a technical leader.

Question 3: "We've adopted the Well-Architected Framework and scored ourselves 85/100 on the AWS review tool. Does that mean our system is well-architected?"

High-Authority Answer:

No. The AWS review tool is a diagnostic, not a verdict. An 85/100 score might mean:

You have strong Security and Reliability (your business priorities), and weak Cost Optimization (intentional trade-off).

Or you have weak Performance and Operational Excellence (because you're a startup and launch velocity matters more).

A 95/100 score on all pillars equally is actually a red flag — it suggests you're over-provisioned, over-engineered, and burning money on pillars that don't matter to your business.

The right question is not "Are we well-architected?" but "Are we architected according to our business priorities?" If Security and Reliability are your pillars, and you score 95 on both with 70 on Cost, that's better than 85 on all five.

"A well-architected system is one that consciously prioritizes the pillars that protect shareholder value and explicitly accepts lower scores on pillars that are secondary. We should never aim for a high score on all pillars — that's over-engineering."

The impostor syndrome: "We didn't score 95, so we must be doing something wrong." The reality: Lower scores on secondary pillars are intentional and defensible business decisions.