Get the Preplance app for a seamless learning experience. Practice offline, get daily streaks, and stay ahead with real-time interview updates.
Get it on
Google Play
4.9/5 Rating on Store
Cloud Basics · Question Set
Real-World Scenarios interview questions for placements and exams.
Questions
14
Included in this set
Subject
Cloud Basics
Explore more sets
Difficulty
Mixed
Level of this set
Go through each question and its explanation. Use this set as a focused practice pack for Cloud Basics.
High availability comes from distributing workloads across multiple Availability Zones. If one zone fails, traffic automatically shifts to healthy instances through a load balancer.
For complete preparation, combine this set with full subject-wise practice for Cloud Basics. You can also explore other subjects and sets from the links below.
Auto Scaling monitors metrics like CPU utilization and scales resources up or down. It ensures consistent performance while minimizing cost.
Combining instance types gives flexibility and savings. Critical services use on-demand or reserved capacity, while background tasks use cheaper spot instances.
Active-active setups run workloads simultaneously in multiple regions. They provide near-zero downtime during outages but cost more to operate.
Choose regions close to your customers for lower latency. Consider data residency laws, available services, and cost differences before deciding.
Failure testing, often called chaos engineering, reveals weak points in infrastructure. By practicing recovery, teams ensure faster response times and more resilient systems.
Start with discovery to map dependencies, then move non-critical workloads first. Use hybrid connectivity like VPN or Direct Connect, test performance, and validate backups before full migration.
Monitoring tracks predefined metrics, while observability allows deeper analysis from logs, traces, and metrics combined. Observability tools help understand unknown failures and complex microservice behaviors.
Apply least-privilege IAM roles, encrypt data, enable logging, and segment networks. Also ensure patching automation and enforce multi-factor authentication for critical access.
First, restore service using rollback or backup. Then conduct a post-mortem to identify the root cause, update runbooks, and improve monitoring to prevent recurrence.
Stateless apps make scaling easy because any instance can handle any request. Session data is stored in external caches or databases instead of local memory.
Automating backups ensures data protection even if an entire region fails. Cross-region replication adds extra durability and disaster recovery coverage.
A three-tier architecture separates presentation, application, and data layers. It improves scalability, maintainability, and fault isolation.
Serverless computing automatically handles scaling and billing per execution. This reduces costs for infrequent or unpredictable workloads.