Physical database design scope: Evaluate the claim: "The physical database design identifies data integrity and security requirements."

Introduction / Context:
Database development progresses from requirements analysis to conceptual and logical design, and then to physical design. Integrity and security requirements are discovered during requirements analysis and refined during conceptual/logical design. Physical design implements these requirements through concrete mechanisms. This question distinguishes between identifying requirements and implementing them.

Given Data / Assumptions:

• Integrity constraints include keys, referential rules, uniqueness, checks.
• Security requirements include authentication, authorization, encryption, auditing, and data masking.
• Physical design decisions include filegroups, partitions, indexes, clustering, compression.

Concept / Approach:
Physical design is about performance, storage, and operational realization. While it implements integrity (e.g., translating unique constraints to indexes) and security (e.g., defining roles, applying encryption at rest), it does not originate or identify the requirements. Those are gathered earlier and expressed in the logical model and security architecture.

Step-by-Step Solution:

Verification / Alternative check:
Review project artifacts: requirements documents and logical ERDs list rules; physical scripts implement them via DDL and security statements.

Why Other Options Are Wrong:

• Correct would conflate requirement identification with implementation.
• Limiting by industry, workload, or encryption does not change the lifecycle responsibility split.

Common Pitfalls:
Skipping early security involvement; assuming the DBA will decide requirements; neglecting validation of implemented controls.

Final Answer:
Incorrect