An online service expects a short, predictable traffic peak during a scheduled event. Which approach best matches this workload pattern?
3 Scalability and Elasticity Online Quiz Questions
Use this free practice quiz with 20 questions to review 3 Scalability and Elasticity, test your knowledge, and prepare for your next test or exam.
A system can be scalable without being elastic if staff can add servers to support growth but must remove them manually after a temporary peak.
- A
True
- B
False
A scaling policy uses CPU percentage as one of its signals. What category of metric does CPU percentage represent?
Increasing CPU or memory on an existing server is , while adding servers or instances to share the work is .
A service can add instances in response to rising demand, but new instances take time to start. What should its design do during that delay?
- A
Remove all existing capacity as soon as a scaling action begins.
- B
Wait until new resources are fully provisioned before serving any requests.
- C
Maintain enough baseline capacity to serve demand while additional resources start.
- D
Avoid scaling because provisioning is not instantaneous.
A system that scales out successfully can always scale in without risking interrupted work, because scaling in simply removes excess capacity.
- A
True
- B
False
Select all statements that accurately describe scalability and elasticity.
- A
Scalability concerns handling a growing workload by increasing capacity.
- B
Elasticity can add and release capacity as demand changes.
- C
Elasticity can use scaling mechanisms to adjust capacity.
- D
Every scalable system automatically releases resources when demand falls.
- E
Scalability and elasticity are opposites, so a system cannot have both.
A web application handles rising demand by adding application instances behind a load balancer. What scaling approach is it using?
For a short, predictable peak, a workload might use . For unpredictable or rapidly changing demand, it might use .
A background job-processing system experiences bursts of queued work, but its workers are not always CPU-bound. Which scaling policy choice is best supported by the workload?
- A
Use CPU utilization as the only signal because it is always the best indicator for every workload.
- B
Use queue depth as a scaling signal because it reflects pending jobs.
- C
Scale in whenever any worker completes a job, regardless of the remaining queue.
- D
Ignore demand signals and keep the worker count fixed.
Select all practices that help a scaling design adapt reliably to changing demand.
- A
Maintain sufficient baseline capacity while new resources start.
- B
Choose signals that reflect the workload being scaled.
- C
Test both scale-out and scale-in behavior.
- D
Assume that scaling actions take effect instantly.
- E
Use CPU utilization as the only possible scaling signal for every workload.
A video-processing service uses a queue of pending jobs. Describe how it could adjust its worker capacity as the queue grows and drains, including a suitable scaling signal and two design considerations for maintaining reliable service.
A team runs an application on Amazon EC2 and wants to add or remove instances according to configured scaling policies. Which statement best describes how an EC2 Auto Scaling group can help?
- A
An EC2 Auto Scaling group only adds CPU or memory to one existing instance.
- B
An EC2 Auto Scaling group is used only for workloads that never change demand.
- C
An EC2 Auto Scaling group can adjust the number of instances according to configured scaling policies.
- D
An EC2 Auto Scaling group automatically guarantees that every application can use added instances effectively.
A web application handles more traffic by adding application instances behind a load balancer so work can be shared. What scaling approach is it using?
A team upgrades an existing server with more CPU and memory to meet a growing workload. Which approach best describes this change?
- A
Horizontal scaling, because the server receives more resources
- B
Vertical scaling, because the existing server receives more resources
- C
Elasticity, because the server must be removed when demand falls
- D
Demand-based scaling, because CPU and memory are being changed
An online service automatically adds application instances during a brief traffic surge and removes them after demand returns to normal. Which concept best describes this behavior?
- A
Scalability, because capacity can only increase for long-term growth
- B
Vertical scaling, because resources are added to an existing server
- C
Elasticity, because capacity rises and falls with demand
- D
Horizontal scaling, because a load balancer distributes requests
A system can be scalable without being elastic if staff can add servers for growth but must remove them manually after a temporary peak.
- A
True
- B
False
A service's workload is expected to grow steadily over the next year rather than fluctuate in short bursts. Which approach is most appropriate?
- A
Plan for scalability by adding capacity or redesigning components as workload grows
- B
Use only scheduled scaling to handle a short peak
- C
Release capacity whenever demand temporarily decreases
- D
Scale in response to queue depth, regardless of the workload
A background job-processing system needs a scaling signal that reflects how much work is waiting to be processed. What signal is especially relevant?
A retailer expects a brief, predictable increase in traffic during a scheduled sale. Which plan best matches this workload pattern?
- A
Use demand-based elasticity only, because the peak is predictable
- B
Schedule an increase before the event and a reduction afterward
- C
Keep peak capacity running permanently to handle the event
- D
Wait until the event ends before adding capacity
Related study packs and tools
- Quiz
2 Digital Logic
A 14-question medium-difficulty quiz on Boolean algebra, logic gates, truth tables, and combinational circuits.
- Study guide
04 Conditionals and Boolean Logic
Learn how Boolean expressions, logical operators, and conditional structures let programs make reliable decisions, including how to handle boundaries, branch order, and testing.
Programming in Java - CS 102Updated - Study guide
05 — Data Structures: Concepts, Operations, and Trade-Offs
A structured guide to the main data structures, their operations, efficiency trade-offs, representations, and practical selection criteria.
- Flashcards
08 — Discrete Mathematics for Computer Science
A focused review of propositional logic, quantifiers, sets, relations, functions, and foundational proof methods in discrete mathematics for computer science.
- Study guide
10 — Data, Systems, and Applications
A progression through how data is organized, searched, exposed through software interfaces, and managed through abstraction layers in modern computer systems.
- Study guide
AP Computer Science A: Integrated Java Problem Solving
A practical review of the integrated Java skills, debugging habits, algorithm reasoning, and free-response strategies needed for AP Computer Science A.
AP Computer Science AUpdated - Study guide
Java ArrayList and Collections: Operations, Traversals, and Algorithms
Learn how to create, modify, traverse, and analyze Java lists with ArrayList, wrapper types, standard algorithms, and the Collections utility class for AP Computer Science A.
AP Computer Science AUpdated - Study guide
Java Inheritance and Polymorphism
A practical guide to Java inheritance, constructor chaining, method overriding, polymorphism, access control, and object behavior for tracing and writing AP Computer Science A programs.
AP Computer Science AUpdated - Study guide
Java Objects, Classes, and the String API
A focused guide to Java classes, object references, constructors, methods, strings, wrapper classes, and API usage for AP Computer Science A.
AP Computer Science AUpdated - Study guide
Packets, Links, and Network Performance
A progressive guide to how packet-switched networks encapsulate data, move it across links, and manage delay, throughput, queues, and congestion.
- Study guide
Parallel and Distributed Computing
A structured guide to designing parallel and distributed systems through decomposition, communication, coordination, state management, scalability, and fault tolerance.
- Study guide
Routing Across Networks
A structured guide to how routers select paths, exchange reachability information, apply routing policy, recover from failures, and diagnose connectivity problems across interconnected networks.