For a shared organizational database, which combination of characteristics is essential to ensure dependable multi-user operation and trust?

Introduction / Context:
A shared database serves many users and applications simultaneously. To maintain trust and continuity of operations, it must fulfill core non-functional requirements beyond mere storage and retrieval.

Given Data / Assumptions:

• Multiple consumers depend on correct, timely data.
• Systems must survive hardware/software issues via recovery strategies.
• Security, integrity, and availability are fundamental.

Concept / Approach:
Shared databases require data quality (accuracy), uptime (availability), resilience (backup and recovery), and protection (security). These collectively support SLAs, compliance, and reliable decision-making.

Step-by-Step Solution:

Verification / Alternative check:
Best practices and standards like ISO 27001 and ITIL emphasize availability, integrity, and confidentiality (AIC) plus disaster recovery planning.

Why Other Options Are Wrong:
Choosing only one property leaves gaps. For example, security without recovery risks data loss; accuracy without availability hinders operations.

Common Pitfalls:
Underestimating backup testing and recovery time objectives; security controls without user training; assuming availability alone ensures data quality.

Final Answer:
All of the above.