Architecture reviews demand precise professional language. This quiz covers the collocations used to propose designs, challenge assumptions, identify trade-offs, and reach consensus.
0 / 5 completed
1 / 5
Fill in: 'The senior engineer was asked to ___ a new event-driven architecture to solve our throughput bottleneck.'
We 'propose an architecture' — 'propose' is the standard verb when formally putting forward a design for review and approval. 'Present' implies delivery to an audience without originating the idea; 'suggest' is too informal for formal architecture work; 'design an architecture' describes the creative act, not the act of putting it forward.
2 / 5
Fill in: 'In the review session, the committee encouraged engineers to ___ the assumptions behind the caching strategy.'
We 'challenge assumptions' — 'challenge' is the professional term for critically examining a premise without implying hostility. 'Question assumptions' is also idiomatic but slightly more informal; 'doubt' suggests personal scepticism rather than structured critique; 'debate' implies two opposing sides rather than testing a single idea.
3 / 5
Fill in: 'Part of the architect's role is to clearly ___ the trade-offs between consistency and availability.'
We 'identify trade-offs' — 'identify' means to formally recognise and name the competing factors that constrain a design decision. 'List' implies simple enumeration without analytical depth; 'find' is informal; 'explain' is what you do after identifying — it is a consequence, not the act itself.
4 / 5
Fill in: 'The Architecture Decision Record exists to ___ the rationale behind every major design choice.'
We 'document decisions' — 'document' is the canonical verb for formally recording information in a structured reference artefact. 'Record' is close but more neutral; 'capture' is slightly more informal; 'store' refers to the act of saving data, not the act of creating a human-readable explanation.
5 / 5
Fill in: 'Before we finalise the design, we need to ___ consensus across all the platform teams.'
We 'seek consensus' — 'seek' pairs with 'consensus' to describe the active process of consulting stakeholders to arrive at agreement. 'Build consensus' is also standard, emphasising the construction process; 'reach consensus' describes the outcome rather than the effort; 'find' is too passive for a deliberate architectural alignment activity.