Context: The final stage of database design is to make the decisions that affect performance, scalability, recovery, security, and the like. This is often called physical database design. A key goal during this stage is data independence, meaning that the decisions made for performance optimization purposes should be invisible to end-users and applications. Physical design is driven mainly by performance requirements, and requires a good knowledge of the expected workload and access patterns, and a deep understanding of the features offered by the chosen DBMS.

Question: What decisions must be made in the last stage of database design?
Answer: performance, scalability, recovery, security

Question: What is an important goal in in this final stage?
Answer: data independence

Question: What factor is reflected in performance requirements?
Answer: Physical design

Question: What decisions are optional in the last stage of database design?
Answer: Unanswerable

Question: What is an irrelevant goal in the final stage?
Answer: Unanswerable

Question: What factor is not reflected in performance requirements?
Answer: Unanswerable

Question: What requires no knowledge of the expected workload?
Answer: Unanswerable

Question: What is no longer a key goal during the final stage?
Answer: Unanswerable