Planning and Design DS0-001 Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   A startup is building a database for a mobile app. The team is using agile development and expects frequent changes to the data model. They want to document the design but are concerned about documentation becoming outdated quickly. What is the best strategy?

   • ASkip documentation until the design is stable
   • BMaintain a living document that is updated as the design evolves
   • CDocument only the final schema, not the rationale
   • DCreate a detailed design document at the start and update it only at major milestones
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A university is redesigning its student information system. The current system has a complex ERD with many entities and relationships. The team wants to simplify the design to make it more maintainable. What is the best approach?

   • AUse a NoSQL database to avoid the need for an ERD
   • BMerge all related entities into a single table to reduce complexity
   • CNormalize the schema to reduce redundancy and ensure data integrity
   • DRemove all relationships from the ERD to simplify it
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A social media company is designing a database to handle user posts, comments, and likes. They expect high write throughput and need to support real-time feeds. The team is considering a NoSQL database with eventual consistency. What is the primary trade-off they must accept?

   • AUsers may see slightly outdated data in feeds, but the system can handle high write volumes
   • BThe database will not be able to handle high write volumes
   • CThe database will be more expensive than a relational database
   • DThe database will require a fixed schema, limiting flexibility
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A regional hospital is planning a new patient management system. Stakeholders include doctors, nurses, billing staff, and IT. During requirement gathering, the doctors emphasize fast retrieval of patient history, while billing staff need detailed audit trails of every change. The IT team warns that storage is limited and the system must be designed to handle growth over the next five years. Which approach best addresses these conflicting needs during the planning phase?

   • AAsk only the IT team for requirements since they understand the system limitations best.
   • BDesign a fully normalized schema with no indexes to save storage space, as storage is limited.
   • CFocus on the doctors' need for speed by creating denormalized tables with no audit trail to maximize performance.
   • DDocument all requirements, then design a normalized schema with an audit table for changes and indexes on frequently queried fields.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A retail company is creating a database for inventory management. The data dictionary needs to define the 'product' entity, which includes attributes like SKU, name, price, and quantity. The team wants to ensure that the data dictionary is useful for both developers and business analysts. What should be included for each attribute?

   • AThe attribute name and its data type only
   • BThe attribute name and an example value
   • CThe attribute name, data type, length, description, and any constraints or business rules
   • DThe attribute name and the table it belongs to only
   Reveal Solution Discussion Select an answer first