Practise the collocations for proposing designs, evaluating trade-offs, documenting decisions, and aligning on architecture.
0 / 5 completed
1 / 5
During the design session, the lead engineer asked the team to ___ a design that would scale to ten million users.
Propose a design is the standard architecture collocation for formally putting forward a technical solution. 'Suggest out' and 'offer around' are informal. 'Raise along' does not convey the structured nature of a design proposal.
2 / 5
The architecture review board required engineers to ___ trade-offs between event-sourcing and a simpler CRUD model.
Evaluate trade-offs is the standard architecture and engineering collocation for systematically assessing the advantages and disadvantages of competing approaches. 'Compare out' and 'check around' are informal. 'Weigh along' is not a standard phrase.
3 / 5
After the architecture meeting, the principal engineer was asked to ___ decisions in the team's ADR repository.
Document decisions is the standard knowledge management collocation for formally capturing the rationale of architectural choices, often in Architecture Decision Records. 'Write down all' and 'note around' are informal. 'Record along' is less precise.
4 / 5
Before development began, all four teams needed to ___ on architecture so that shared interfaces would be consistent.
Align on architecture is the standard cross-team engineering collocation for reaching a shared understanding of technical direction. 'Agree out' and 'settle around' are informal. 'Sync along' is too informal for a formal alignment process.
5 / 5
The staff engineer used Miro boards to help the team ___ the proposed hexagonal architecture before committing to it.
Visualise the architecture is the standard engineering communication collocation for representing a design visually to aid understanding. 'Draw along' and 'sketch out around' are informal. 'Map away' does not convey the deliberate communication intent.