Lifecycle duration reality: Assess the statement: "The longest step of database development is database maintenance."
-
ACorrect
-
BIncorrect
-
CCorrect only for cloud-hosted systems
-
DCorrect only if the database is mission-critical
-
ECorrect only when the design is poor
Answer
Correct Answer: Correct
Explanation
Introduction / Context: Software and database systems spend the majority of their lifecycle in operation and maintenance, not initial build. Maintenance encompasses monitoring, optimization, patching, backup/restore validation, capacity planning, and enhancements. This question checks awareness of lifecycle economics.
Given Data / Assumptions:
- Deployment is followed by months or years of operation.
- Change is continuous (new features, schema evolution, workload shifts).
- Reliability and performance work persists throughout the lifespan.
Concept / Approach: The cost and time distribution of database development skews towards the post-deployment phase. Even well-architected systems require ongoing tuning (indexes/statistics), security maintenance, data lifecycle management (archival/purge), and compliance tasks, which cumulatively exceed initial development effort.
Step-by-Step Solution:
Estimate build time (weeks to months) vs. run time (years).List recurring tasks: backups, integrity checks, index maintenance, upgrades.Consider scaling: data growth and workload variation increase maintenance activities.Conclude that maintenance duration dominates.Verification / Alternative check: Review budget allocations and time tracking across project phases; operations typically represent the largest share.
Why Other Options Are Wrong:
- Limiting the statement to cloud, mission-critical, or poor design is unnecessary; even good on-prem systems require significant maintenance.
Common Pitfalls: Underfunding operations; neglecting observability; failing to automate maintenance; ignoring data lifecycle policies.
Final Answer: Correct