Which of the following architectures is most suitable to provide redundancy for critical business processes?

Question

Options

• ANetwork-enabled
• BServer-side
• CCloud-native
• DMultitenant

• A
  3% (1)
• C
  94% (31)
• D
  3% (1)

Explanation

Cloud-native architecture is most suitable for redundancy because it is designed from the ground up to leverage distributed cloud infrastructure - including built-in failover, auto-scaling, load balancing, and multi-region replication - making it ideal for keeping critical business processes highly available.

Network-enabled (A) simply means a system can communicate over a network; it says nothing about redundancy or fault tolerance. Server-side (B) refers to where processing occurs, not how resilient or redundant the system is - a single server-side app can be a single point of failure. Multitenant (D) describes how multiple customers share the same infrastructure, which is a cost/isolation model, not a redundancy strategy.

Memory tip: Think "cloud = redundancy by default" - cloud-native apps are built to survive hardware failures, traffic spikes, and regional outages, which is exactly what critical business processes demand.

No community discussion yet for this question.