Learn the collocations for modelling data, designing schemas, normalising tables, and optimising queries.
0 / 5 completed
1 / 5
Before building the API, the backend team spent a day to ___ data as entities and relationships in an ER diagram.
Model data is the standard database design collocation for representing real-world entities and their relationships in a formal data model. 'Design along' and 'draw around' are informal. 'Plan out' is too generic for data modelling.
2 / 5
The database architect worked with the team to ___ schema for the new multi-tenant SaaS platform.
Design schema is the standard database engineering collocation for defining the structure of tables, columns, and relationships. 'Create along' and 'plan away' are informal. 'Build out around' is redundant and not standard.
3 / 5
The data engineer recommended splitting the user_orders table to ___ tables and eliminate data redundancy.
Normalize tables is the standard database design collocation for applying normal forms to eliminate redundancy and improve data integrity. 'Clean along' and 'simplify around' are too vague. 'Fix out' is not a valid phrase.
4 / 5
The DBA added composite indexes to ___ queries that were taking over two seconds to return results.
Optimize queries is the standard database performance collocation for improving the execution speed and resource usage of SQL statements. 'Speed up around' and 'improve along' are informal. 'Fix out' is not used in a database context.
5 / 5
The team used Flyway to ___ migrations in version control so that schema changes were reproducible.
Track migrations is the standard database DevOps collocation for managing schema changes as versioned, executable migration scripts. 'Record along' and 'store around' are informal. 'Keep out' is not a standard phrase.