Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Hybrid Cloud for Compliance and Elastic Scaling
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 enterprise maintains legacy database systems in an on-premises datacenter due to strict regulatory data governance policies. The company plans to launch a new, highly scalable customer-facing web application that experiences unpredictable traffic surges and wants to avoid purchasing additional physical server hardware.
Which cloud deployment model should the enterprise implement to satisfy both requirements?
Explanations
Community cloud
Community cloud
What a Community Cloud Is
A community cloud is a shared cloud infrastructure tailored for a specific group of organizations that have shared concerns, such as common mission goals, security requirements, policies, or compliance considerations. It may be managed by the participating organizations or a third-party vendor.
Why It Doesn't Meet the Requirement
A community cloud does not specifically resolve the organization's need to bridge its own proprietary on-premises infrastructure with an elastic public cloud platform. It introduces joint governance models that are unnecessary for standard commercial web scaling.
Key Characteristics and Limitations
- Shared Industry Focus: Designed for specific consortia, such as government agencies, healthcare networks, or financial institutions.
- Shared Cost Burden: Capital and operational expenses are distributed among participating community members.
- Complex Governance: Requires joint management agreements and standardized compliance frameworks across distinct entities.
- Not an Architectural Bridge: Does not inherently describe the integration between an enterprise's private datacenter and public cloud resources.
This Answer Would Be Correct If
Multiple independent enterprises within the same industry needed to collaborate by sharing a dedicated, jointly funded cloud environment with identical regulatory frameworks.
Hybrid cloud
Hybrid cloud
What a Hybrid Cloud Model Is
A hybrid cloud combines public cloud services (such as Microsoft Azure) with private cloud or on-premises infrastructure. This model allows data and applications to be shared between both environments using secure network interconnects such as Azure ExpressRoute or Site-to-Site VPN gateways.
How It Meets the Organization's Requirements
- Regulatory Compliance: Retains sensitive legacy databases within the on-premises datacenter to strictly adhere to regulatory and data sovereignty standards.
- Elastic Scaling: Hosts the customer-facing web tier in the public cloud to handle rapid, unpredictable traffic spikes without purchasing fixed physical capacity.
- Cost Efficiency: Reduces upfront capital expenditure (CapEx) for web hosting while maximizing the return on existing on-premises investments.
Key Advantages and Capabilities
- Operational Flexibility: Enables workloads to run where they operate most effectively based on compliance, performance, or cost constraints.
- Seamless Integration: Facilitates unified identity, monitoring, and networking across diverse environments.
- Gradual Migration: Allows organizations to modernize applications iteratively without requiring an immediate, disruptive transition.
- Resource Optimization: Balances steady-state baseline computing on-premises with cloud bursting for peak demands.
Why This Model Is Optimal
A hybrid cloud provides the ideal architectural trade-off by preserving direct governance and security control over existing legacy assets while unlocking the elasticity, consumption-based pricing, and global scale of the public cloud.
Public cloud
Public cloud
What the Public Cloud Is
A public cloud is an environment entirely owned and operated by a third-party cloud provider, such as Microsoft. Computing resources, storage, and networking hardware are hosted across global datacenters and delivered to multiple tenants over the internet on a pay-as-you-go operational expenditure (OpEx) model.
Why It Doesn't Meet the Requirement
While the public cloud easily supports rapid scalability and eliminates upfront hardware purchases for the web application, moving entirely to a public cloud would violate the requirement to retain the legacy databases within the organization's existing on-premises datacenter for regulatory compliance.
Key Characteristics and Limitations
- Multi-Tenancy: Underlying physical hardware is shared securely among multiple customer organizations.
- Offloaded Maintenance: Hardware lifecycle, physical security, and datacenter operations are fully managed by the provider.
- Data Residency Constraints: Workloads must be configured within specific geographic regions to comply with local regulations.
- All-in Cloud Footprint: Does not by itself account for connected on-premises systems without establishing hybrid architecture.
This Answer Would Be Correct If
The enterprise decided to fully decommission its local datacenter and migrate all systems, including databases and web tiers, directly to cloud-native services in Azure.
Private cloud
Private cloud
What a Private Cloud Is
A private cloud consists of computing resources used exclusively by a single business or organization. It can be physically located at an organization's on-premises datacenter or hosted by a dedicated third-party service provider.
Why It Doesn't Meet the Requirement
A private cloud requires the organization to procure, provision, and maintain all physical hardware. This relies heavily on upfront capital expenditure (CapEx) and restricts the elasticity needed to accommodate rapid, unpredictable web application surges without purchasing surplus physical servers.
Key Characteristics and Limitations
- Dedicated Infrastructure: Hardware and networks are dedicated entirely to one tenant, providing complete control over configurations.
- High Maintenance Overhead: The organization is fully responsible for ongoing hardware maintenance, power, cooling, and operational staffing.
- Limited Elasticity: Scaling capacity requires purchasing, installing, and configuring additional physical infrastructure.
- Significant Upfront Investment: Requires substantial capital expenditure prior to deploying new workloads.
This Answer Would Be Correct If
The organization had an absolute mandate requiring complete physical isolation and full hardware management for all application tiers with no external internet cloud connectivity.
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
Hybrid Cloud Model
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Hybrid Cloud CapEx vs OpEx
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Public Cloud
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure ExpressRoute
Define cloud models, including public, private, and hybrid
IntermediateAZ-204 Developing Solutions for Microsoft Azure Exam
Azure Blob System Properties vs User-Defined Metadata
Set and retrieve properties and metadata
Last updated Validated