Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Horizontal Autoscale with CPU-Based Scaling Rules
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An e-commerce company experiences unpredictable surges in web traffic during flash sales events, followed by periods of low activity during standard business hours. The company wants an automated solution that dynamically adds virtual machine instances when average CPU utilization exceeds 75% and removes instances when demand drops, ensuring optimal performance while reducing compute costs.
Which scaling strategy should the company implement?
Explanations
Vertical scaling by increasing hardware size
Vertical scaling by increasing hardware size
What Vertical Scaling Is
Vertical scaling (scaling up and scaling down) involves keeping the total count of resource instances constant while changing their individual hardware capacity by adding or removing CPU cores, RAM, disk space, or network bandwidth.
Why It Doesn't Meet the Requirement
- No automated elasticity: Vertical scaling cannot dynamically and seamlessly add or remove compute instances on demand based on metric thresholds like CPU usage.
- Potential downtime: Resizing a virtual machine often requires a system restart, causing temporary service interruptions that degrade user experience during a flash sale.
- Hard hardware limits: Vertical scaling is constrained by the maximum hardware specifications available in an Azure region, preventing workloads from scaling smoothly beyond a single machine's ceiling.
Key Characteristics and Limitations
- Fixed instance count: Changes the capacity of existing nodes rather than expanding the fleet horizontally.
- Hardware ceilings: Workloads eventually encounter physical hardware boundaries that limit further upward growth.
- Restricted regional availability: High-end VM sizes may not be uniformly offered across every Azure region.
This Answer Would Be Correct If
A database or monolithic legacy application cannot distribute its workload across multiple instances and requires a higher single-node capacity of memory or processing power to handle larger internal workloads.
Additional Context
While vertical scaling improves the processing power of a single node, cloud-native architectures generally favor horizontal scaling for web tiers due to better resilience, elastic flexibility, and zero downtime during scale actions.
Horizontal autoscaling using metric-based rules
Horizontal autoscaling using metric-based rules
What Horizontal Autoscaling Is
Horizontal autoscaling (scaling out and scaling in) is the process of dynamically allocating and deallocating resource instances, such as adding or removing virtual machines within a Virtual Machine Scale Set or Azure App Service, based on workload demand.
How It Meets the Requirements
- Automated instance adjustment: Dynamic autoscale rules continuously monitor real-time performance telemetry and trigger automated scale actions without manual administrative intervention.
- Metric threshold triggering: The company can configure metric rules to scale out by adding new VM instances whenever CPU usage exceeds 75%, maintaining low latency during traffic spikes.
- Cost minimization: When user demand subsides, autoscale scales in by deallocating excess VM instances, ensuring the organization only pays for the compute capacity it actually consumes.
Key Advantages and Capabilities
- Elastic resource management: Provides broad flexibility in cloud environments by allowing workloads to grow horizontally across dozens or hundreds of identical instances.
- Metric and schedule support: Supports scaling triggers based on various resource metrics (like CPU utilization, memory usage, and queue length) or predefined calendar schedules.
- Built-in safety boundaries: Enforces configured minimum and maximum instance limits to prevent uncontrolled cloud spending while guaranteeing base service capacity.
- Automated notifications: Integrates with notification pipelines like webhooks and email alerts to inform operations teams whenever a scale event occurs.
Why This Is Optimal
Horizontal autoscaling is the optimal choice because it dynamically aligns infrastructure supply with real-time customer demand. Unlike fixed capacity or vertical hardware resizing, scaling horizontally avoids application downtime, provides elastic throughput during unexpected surges, and automatically curtails operational costs during idle periods.
Cross-region replication to a paired region
Cross-region replication to a paired region
What Cross-Region Replication Is
Cross-region replication to a paired region is a disaster recovery and business continuity strategy where application data and services are duplicated across geographic regions separated by hundreds of miles.
Why It Doesn't Meet the Requirement
- Disaster recovery focus: Paired regions protect workloads against regional outages and major natural disasters rather than managing dynamic, real-time traffic fluctuations.
- No metric-based instance scaling: Deploying secondary instances across paired regions does not automatically add or remove compute capacity based on CPU thresholds.
- Increased baseline cost: Maintaining duplicate resources in another region without autoscaling increases continuous infrastructure spending instead of optimizing costs.
Key Characteristics and Limitations
- Geographic separation: Azure paired regions are typically separated by at least 300 miles to withstand broad geographical disasters.
- Sequential updates: Azure rolls out platform maintenance updates sequentially across paired regions to avoid concurrent downtime.
- Traffic routing integration: Relies on global load balancers like Azure Traffic Manager or Azure Front Door to route users during failovers.
This Answer Would Be Correct If
The scenario required protecting critical business operations against a complete regional datacenter outage or meeting geographic data residency and compliance regulations.
Additional Context
Cross-region replication enhances high availability and disaster recovery, but it must be combined with horizontal autoscaling within each region to adapt to fluctuating traffic loads efficiently.
Azure Resource Manager resource locks
Azure Resource Manager resource locks
What Azure Resource Manager Resource Locks Are
Azure Resource Manager (ARM) resource locks are administrative controls used to safeguard critical Azure resources, subscriptions, or resource groups from accidental deletion or unintended modifications.
Why It Doesn't Meet the Requirement
- Governance tool only: Resource locks manage control-plane access permissions and do not perform compute operations or handle application performance.
- No scaling capabilities: Locks cannot monitor performance metrics (such as CPU or memory usage) or dynamically provision new resources.
- Can restrict scaling: Applying a
ReadOnlyorCanNotDeletelock at the resource group level can actually block autoscaling mechanisms from creating or deleting VM instances.
Key Characteristics and Limitations
- Lock types: Available primarily as CanNotDelete (users can read and modify, but not delete) and ReadOnly (users can read, but cannot modify or delete).
- Scope inheritance: Locks applied at a subscription or resource group scope automatically cascade down to all enclosed child resources.
- Administrative safeguard: Designed purely for governance, compliance, and human error mitigation.
This Answer Would Be Correct If
An administrator needs to prevent team members from accidentally deleting a core production database or modifying an established virtual network infrastructure.
Additional Context
ARM resource locks are a vital part of cloud governance, but scaling and performance optimization are handled by services such as Azure Monitor autoscale and Virtual Machine Scale Sets.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Combining Autoscaling and High Availability
Describe the benefits of high availability and scalability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Availability Zones
Describe the benefits of high availability and scalability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Virtual Machine Scale Sets
Describe the benefits of high availability and scalability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Autoscaling and High Availability
Describe the benefits of high availability and scalability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model Physical Security
Describe the shared responsibility model
ExpertAZ-305 Designing Microsoft Azure Infrastructure Solutions Exam
Azure Container Apps vs AKS
Recommend a container-based solution
Last updated Validated