Database Activities — Retrieval and Operational Use Which database activity corresponds to the stage at which data are actually stored, retrieved, and used by applications and end users?

Introduction:
While earlier phases define what the database should contain and how it should be structured, organizations derive value only when the system is implemented and put into active use. This question distinguishes design-time activities from runtime operation and retrieval.

Given Data / Assumptions:

• We are asked to identify the activity that enables real data retrieval and use.
• Other options are planning or design phases that precede implementation.
• Implementation implies deployment, population, and operational access.

Concept / Approach:
Database implementation covers creating physical structures, loading data, configuring security, and enabling applications to connect and execute queries. Only at this stage do users and systems retrieve and manipulate data in production. The earlier stages are necessary precursors but do not provide operational access by themselves.

Step-by-Step Solution:
1) Eliminate planning phases (enterprise modeling, strategic planning).2) Eliminate design phases (logical and physical design) that produce specifications.3) Select the phase where the database is deployed and accessed: database implementation.

Verification / Alternative check:
Implementation checklists include CREATE statements, indexing, data load, user provisioning, and integration with applications—activities tied directly to retrieval and use.

Why Other Options Are Wrong:

• Enterprise modeling / Strategic data planning: Scope and strategy, not operations.
• Logical design: Abstract schema, no physical access yet.
• Physical design and definition: Produces DDL and structures but still not operational until implemented.

Common Pitfalls:
Assuming that physical design equals production availability; implementation is the step that activates the system for real users.

Final Answer:
Database implementation