Data Modeling easy
In the design phase, what is an 'ER Diagram' used for?
- A Generating precise, real-time estimations of the monthly cloud infrastructure and egress costs for a globally distributed storage cluster.
- B Visualizing the system's logical Entities (tables), their distinctive Attributes (columns), and the structural Relationships between them.
- C Prototyping the high-fidelity user interface (UI) and navigation wireframes for the application's mobile and desktop web dashboards.
- D Measuring and benchmarking the average network latency and packet loss rates across several interconnected regional data centers.
Answer: B. Visualizing the system's logical Entities (tables), their distinctive Attributes (columns), and the structural Relationships between them.
Entity-Relationship (ER) Diagrams serve as the technical blueprint for a database's structure. By mapping out how data elements interact (e.g., 'A User can own many accounts, but each account has exactly one owner') before any code is written, engineers can ensure the schema is logically sound, normalized, and capable of supporting the application's functional requirements without costly future rework.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- When modeling a Distributed Transaction using the Saga Pattern (Choreography or Orchestration), what type of consistency do you achieve?
- Which practice prevents SQL Injection attacks?
- What is 'Bi-Temporal' data modeling (e.g., in SQL:2011 standard)?
- Adding an Index to a database column generally improves Read performance. What is the negative trade-off?
- Log Systems Merge (LSM) Trees (used in RocksDB, Cassandra) optimize for fast writes. What is their primary downside regarding Disk I/O?
- What is the primary objective of normalizing a relational database schema (e.g., to 3NF)?