Master the collocations for conducting, presenting, and documenting architecture reviews.
0 / 5 completed
1 / 5
The tech lead was asked to ___ an architecture review before the new data pipeline went into production.
Conduct an architecture review is the formal collocation used in engineering governance. 'Conduct' pairs with formal processes and reviews. 'Do up' is informal. 'Run through' implies a quick walkthrough, not a formal review. 'Perform out' is not standard.
2 / 5
The CTO asked the team to ___ an architecture review for next Thursday.
Schedule a review is the natural professional collocation. Reviews are 'scheduled' like meetings. 'Book in about' is ungrammatical. 'Plan along' and 'set along' are not valid collocations in this context.
3 / 5
The architect was asked to ___ the new event-driven design to the review board.
Present (a design) to a review board is the correct professional collocation. 'Show off' has a boastful connotation. 'Display at' is more visual/physical. 'Exhibit' is used in galleries and trade shows, not engineering reviews.
4 / 5
After the meeting, the architect was expected to ___ the decisions and trade-offs in the RFC.
Document decisions is the standard technical collocation for capturing outcomes formally. 'Write away' is informal and directional. 'Note down all' is redundant. 'Record into' is not a standard phrase in this context.
5 / 5
The team agreed to ___ the architecture review in six months to check if the decisions held up.
Follow up on a review is the standard project management collocation for revisiting and tracking outcomes. 'Check back about' is informal. 'Revisit after' is possible but 'revisit the review' is more idiomatic. 'Return for' doesn't convey a formal follow-up.