Cloud+ V3 Compute Sizing and Scaling Basics

1. A web application experiences 80% CPU utilization during peak hours. What scaling action is most appropriate?

Immediately add 10 instances

Scale up to a larger instance type

Add instances based on a policy threshold

Reduce instance memory

Submit

6. What does 'burstable' instance performance mean in cloud computing?

Instances that fail intermittently

Instances that scale up temporarily when demand increases

Instances with limited baseline CPU and ability to burst above it

Instances that only work for short durations

7. When designing a multi-region cloud architecture, what is a key consideration for compute sizing?

Using identical instance sizes in all regions

Regional demand patterns and latency requirements

Always choosing the smallest instances

Avoiding auto-scaling entirely

8. Spot instances are best suited for which type of workload?

Mission-critical production applications

Fault-tolerant, flexible-timing batch jobs

Real-time transactional systems

Interactive user-facing applications

9. What is the main benefit of using container orchestration platforms for scaling workloads?

Automatic resource allocation and scaling based on demand

Elimination of all networking overhead

Guaranteed zero latency

Simplified database management

10. Which cloud service model allows the most control over compute sizing and scaling decisions?

SaaS

PaaS

IaaS

FaaS

11. Which metric is most critical when determining the appropriate compute instance size for a CPU-intensive workload?

Network bandwidth

VCPU count and processing power

Storage capacity

Memory type

12. In cloud architecture, what does 'right-sizing' an instance mean?

Choosing the largest available instance

Matching instance type and size to actual workload needs

Using only GPU instances

Minimizing all resource allocation

13. Reserved instances are most cost-effective for workloads with which characteristic?

Highly variable and unpredictable demand

Predictable, consistent baseline usage

Seasonal peaks only

Single short-term projects

14. Which load balancing algorithm distributes traffic equally across all available instances?

Least connections

Round robin

Weighted round robin

IP hash

15. When sizing compute instances for a database workload, which factor is typically prioritized?

GPU availability

Memory capacity and I/O performance

Storage encryption

Network bandwidth only

16. What is the purpose of setting a cooldown period in auto-scaling policies?

Prevent rapid scaling fluctuations and reduce cost

Increase instance memory automatically

Encrypt traffic between instances

Monitor database performance

17. Which scaling metric is best suited for handling sudden traffic spikes in a web application?

Schedule-based scaling

Request count per instance

Disk I/O utilization

Network packet loss

18. In a load-balanced environment, what does session affinity (sticky sessions) ensure?

All user requests route to the same backend instance

Encrypted communication between client and server

Reduced database queries

Faster network throughput

19. Auto-scaling policies typically use which of the following triggers to add or remove instances?

Manual administrator requests only

CPU utilization, memory usage, and request count

Database size metrics

User login frequency

20. What is the primary advantage of horizontal scaling over vertical scaling in cloud environments?

Lower cost and no downtime during scaling

Simpler architecture and fewer components

Better security posture

Reduced network latency

Cloud+ V3 Compute Sizing and Scaling Basics Quiz