Where are servers typically provisioned for large-scale systems?
In personal computers owned by the company
In shared office spaces
In company-owned data centers or cloud service providers
On physical tape storage
What is a key advantage of cloud services like AWS for server provisioning?
Physical access to the servers
Unlimited free server time
On-demand server provisioning and cost control
Elimination of all potential server downtime
What is a major downside of a cold standby backup system?
High cost of server maintenance
Requires a replicated live database
Significant downtime and potential data loss
Complexity of implementation
Why might a cold standby system still be used despite its limitations?
It provides seamless failover capabilities
It is suitable for critical production systems
It is a cost-effective and simple solution for non-critical systems
It eliminates the need for backups
What is the primary difference between a warm standby and a cold standby system?
Warm standby uses simultaneous writes to all hosts
Warm standby relies on live replication instead of periodic backups
Cold standby offers faster recovery times
Warm standby requires manual intervention to activate
What is one potential drawback of using a warm standby system?
High probability of data loss
Increased load on the backup database
Lack of replication options in modern databases
Long downtime during failover
What is the key characteristic of a hot standby system?
Writes are replicated periodically
It relies on cold backups for recovery
Data is written simultaneously to all database hosts
It eliminates the need for read scaling
How does a hot standby system support horizontal scaling?
By distributing write operations among multiple servers
By enabling simultaneous read operations across database hosts
By relying on a single database host with backups
By using a replication mechanism to synchronize data
What is the main advantage of serverless services like AWS Lambda?
Complete elimination of downtime
Direct control over physical servers
Abstraction of server provisioning and billing based on usage
Reduced costs due to fixed pricing models
Which scenario best fits a serverless architecture?
Running long-term, stateful applications
Handling unpredictable, short-lived workloads
Managing a large database with replication
Provisioning dedicated servers for high-traffic websites