70-465 · Question #160
70-465 Question #160: Real Exam Question with Answer & Explanation
The correct answer is B: Create a new table named Sales.OrderStatus that contains three columns named OrderID,. This question tests the ability to design a normalized database schema that tracks order status history while minimizing storage overhead.
Question
You are designing a Windows Azure SQL Database for an order fulfillment system. You create a table named Sales.Orders with the following script. Each order is tracked by using one of the following statuses: - Fulfilled - Shipped - Ordered - Received You need to design the database to ensure that that you can retrieve the following information: - The current status of an order - The previous status of an order. - The date when the status changed. - The solution must minimize storage. More than one answer choice may achieve the goal. Select the BEST answer.
Options
- ATo the Sales.Orders table, add three columns named Status, PreviousStatus and ChangeDate.
- BCreate a new table named Sales.OrderStatus that contains three columns named OrderID,
- CImplement change data capture on the Sales.Orders table.
- DTo the Sales.Orders table, add three columns named FulfilledDate, ShippedDate, and ReceivedDate.
Explanation
This question tests the ability to design a normalized database schema that tracks order status history while minimizing storage overhead.
Common mistakes.
- A. Adding Status, PreviousStatus, and ChangeDate columns directly to Sales.Orders only stores one level of history (current and one previous status), which is a denormalized design that does not scale well and wastes storage if more history is ever needed.
- C. Change Data Capture (CDC) is a heavy auditing mechanism designed for data replication and ETL scenarios, not for application-level status tracking; it incurs significant storage and processing overhead, violating the requirement to minimize storage.
- D. Adding FulfilledDate, ShippedDate, and ReceivedDate columns stores dates but not a flexible status field, requires schema changes for new statuses, and does not directly provide the previous status without complex logic, making it less efficient and less maintainable.
Concept tested. Normalized relational schema design for status history tracking
Reference. https://learn.microsoft.com/en-us/azure/azure-sql/database/design-first-database-tutorial
Topics
Community Discussion
No community discussion yet for this question.