In order to ensure that you can maintain high availability in the face of server failure, you should implement which of the following?

Question

Options

• ASharding
• BProperly defined user roles
• CReplication
• DPut indexes on all of your documents
• EThe proper storage engine

• A
  3% (1)
• B
  3% (1)
• C
  95% (38)

Explanation

Replication ensures high availability by maintaining copies of your data across multiple servers, so if one server fails, another can immediately take over without downtime or data loss. Sharding (A) distributes data across servers for scalability, but a shard going down means that portion of data becomes unavailable - it solves scale, not fault tolerance. User roles (B) address security and access control, which are unrelated to uptime. Indexing all documents (D) improves query performance but has no bearing on server failure recovery, and over-indexing can actually hurt write performance. The storage engine (E) affects performance characteristics and features but does not itself provide redundancy against server failure.

Memory tip: Think "Replication = Redundancy = Resilience" - all three R's. If you have a replica, you always have a backup ready to go when the primary goes down.

No community discussion yet for this question.