Software architecture practice assessment. Foundations

Scenario: A change in billing breaks support tooling. What does that suggest?

A proposal says 'scalable' with no constraint. What is the correct response?

Teams argue about microservices vs monolith. What makes it an architectural question?

Scenario: A diagram is beautiful but nobody can use it to debug or change the system. What failed?

Scenario: Two teams keep breaking each other’s releases. What is the most likely root cause?

Which statement is most defensible about architecture decisions?

A useful architecture diagram should primarily answer:

Scenario: A requirement says 'high availability' but gives no target. What is the correct next step?

Scenario: A shared database becomes the integration mechanism across services. What is the main risk?

Scenario: A design optimises for speed, but auditability suffers. What should happen?

Scenario: One team owns a component but cannot ship without 5 other teams. What does that suggest?

Scenario: You must convince a skeptical stakeholder. What makes architecture evidence credible?