Lifecycle applicability: Consider the claim: "The systems development life cycle (SDLC) cannot be used with database implementation."

Introduction / Context:
The systems development life cycle (SDLC) is a structured approach covering planning, analysis, design, implementation, testing, deployment, and maintenance. Databases are core system components, and their development aligns naturally with SDLC phases. This question checks whether you understand that SDLC absolutely applies to database work.

Given Data / Assumptions:

• Database artifacts include conceptual/logical/physical models, DDL, ETL processes, and administration procedures.
• Quality attributes (performance, availability, security) must be engineered like any other system component.
• Governance and change control are in place.

Concept / Approach:
During analysis, requirements for data entities, integrity, and access are gathered. Logical design refines entities and relationships. Physical design maps to storage structures, indexes, and partitions. Implementation deploys schema and data movement. Testing validates constraints, performance, and recovery. Deployment and maintenance address backups, patching, and optimization. SDLC thus provides a rigorous framework for database projects.

Step-by-Step Solution:

Verification / Alternative check:
Review successful database programs that use SDLC artifacts (data dictionaries, migration plans, rollback strategies).

Why Other Options Are Wrong:

• Claims that SDLC does not apply to NoSQL, DW, or prototypes are unfounded; SDLC is methodology-agnostic and can be iterative or agile.

Common Pitfalls:
Treating database work as an afterthought; skipping modeling; deploying without performance and recovery testing.

Final Answer:
Incorrect