Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
How Resource Region Egress and Support Drive Azure Costs
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.
A company is planning to migrate its on-premises web application and database workloads to Microsoft Azure. During the architecture and budgeting phase, the cloud team needs to identify the fundamental factors that will determine the recurring monthly expenditure for the new cloud environment.
Which set of factors directly influences the overall costs incurred when running services in Azure?
Explanations
Azure portal theme settings, multi-factor authentication registration methods, custom RBAC role definitions, and tenant domain names
Azure portal theme settings, multi-factor authentication registration methods, custom RBAC role definitions, and tenant domain names
What Portal Settings and Identity Features Are
Azure portal personalization, multi-factor authentication (MFA) registration, custom Role-Based Access Control (RBAC) roles, and custom domain bindings are user interface preferences and directory identity management features within Microsoft Entra ID and the Azure platform.
Why It Doesn't Meet the Requirement
Personalization preferences and foundational identity controls do not drive infrastructure consumption charges:
- Portal display themes and user interface configurations are client-side visual settings that are completely free.
- RBAC role definitions manage authorization across Azure Resource Manager and do not incur administrative fees.
- Tenant domain names verify domain ownership in Microsoft Entra ID and do not add computing or data transfer charges.
- While advanced identity governance features may require specific Microsoft Entra ID user licensing tiers, basic MFA methods and role assignments themselves are not primary cost drivers for hosting cloud workloads.
Key Characteristics and Limitations
- Administrative focus: Primarily handle identity security, directory federation, and user accessibility.
- No infrastructure metering: These settings do not generate compute runtime, data egress, or capacity-based billing meters.
- Fixed control plane utility: Portal configurations operate on the control plane rather than the data or infrastructure layer.
This Answer Would Be Correct If
A scenario asked for security administration and user interface personalization options that control access permissions and presentation styles in Azure.
Source code repository size, client web browser versions, DNS zone record quantities, and virtual machine operating system build numbers
Source code repository size, client web browser versions, DNS zone record quantities, and virtual machine operating system build numbers
What Development and Client Environment Attributes Are
Source code repositories, client web browsers, DNS record counts, and guest OS minor build revisions describe developer tooling, end-user client software, and specific software environment details.
Why It Doesn't Meet the Requirement
These operational characteristics do not represent primary drivers of core Azure infrastructure spending:
- Client browser versions have no effect on how Azure provisions, meters, or bills cloud services.
- Operating system build numbers (such as specific minor patch updates) do not alter the base licensing or compute rate of the virtual machine.
- Source code repository storage is typically managed within source control platforms (like GitHub or Azure DevOps) and is distinct from Azure resource infrastructure hosting meters.
- DNS record counts within basic private or public zones are either billed at negligible tier thresholds or free depending on the DNS provider, rather than serving as core infrastructure cost drivers.
Key Characteristics and Limitations
- Client-side decoupling: Azure billing is entirely isolated from the end user's local computing environment and web browser choice.
- Patch level independence: Virtual machine compute pricing is determined by size tier (vCPUs, RAM) and operating system type (e.g., Windows vs. Linux), not minor build versions.
- Developer tool separation: Source code size does not directly dictate cloud execution and operational infrastructure expense.
This Answer Would Be Correct If
A scenario focused on client-side compatibility requirements and local software development prerequisites for accessing cloud management tools.
Resource type and configuration, geographic deployment region, outbound network data transfer, and selected Azure support plan
Resource type and configuration, geographic deployment region, outbound network data transfer, and selected Azure support plan
What Azure Cost Drivers Are
Azure cost drivers are the fundamental parameters and operational variables that determine how Microsoft meters and charges for cloud resource consumption. Rather than charging a flat fee for all services, Azure calculates costs based on specific consumption dimensions tailored to resource specifications and architectural decisions.
How These Factors Determine Expenditure
Each identified element impacts total monthly spend through distinct metering mechanisms:
- Resource Type and Configuration: Different service offerings (such as compute virtual machines, managed SQL databases, or serverless functions) consume different hardware resources, software licenses, and performance tiers (CPU, memory, storage IOPS), each carrying specific hourly or per-transaction pricing.
- Geographic Region: Infrastructure, real estate, energy, and taxation costs vary across global data center locations, leading to regional price differences for identical Azure resources.
- Outbound Data Transfer (Egress): While inbound data transfers (ingress) into Azure data centers are typically free, outbound data transfer across billing zones, inter-region links, or to the public internet incurs bandwidth costs.
- Selected Support Plan: Azure includes free basic support for billing and subscription management, but upgraded technical support tiers (such as Developer, Standard, or Direct) add recurring monthly charges to the overall invoice.
Key Advantages and Cost Considerations
- Granular cost tracking: Organizations can monitor specific meters like compute runtime, storage volume, and data movement.
- Architectural optimization: Workloads can be placed in cost-effective regions and sized according to actual performance needs.
- Bandwidth management: Isolating traffic within the same region or virtual network minimizes outbound bandwidth fees.
- Tailored support alignment: Companies only pay for enhanced operational support when higher service-level response times are required.
Why This Option Is Optimal
This combination encapsulates the primary technical and commercial drivers of Azure infrastructure expenses. Factoring in compute configurations, geographic location, network egress, and support tiers provides the most comprehensive and accurate baseline for total cost estimation.
Management group hierarchy depth, resource group naming conventions, private IP subnet ranges, and assigned Azure Policy initiatives
Management group hierarchy depth, resource group naming conventions, private IP subnet ranges, and assigned Azure Policy initiatives
What Governance and Management Constructs Are
Azure management groups, resource group naming standards, private IP addressing schemas, and Azure Policy definitions represent administrative, organizational, and governance mechanisms within the Azure Resource Manager framework.
Why It Doesn't Meet the Requirement
These management and governance features are complimentary platform capabilities that do not incur direct consumption charges:
- Management groups and resource groups are logical containers used for access control and organization; creating or nesting them does not cost money.
- Resource naming conventions and internal private IP address assignments are structural metadata and networking configurations that carry zero direct billing impact.
- Azure Policy is a built-in governance engine that audits and enforces compliance across resources without adding a per-rule or per-evaluation charge.
Key Characteristics and Limitations
- Pure governance tools: Facilitate organizational hierarchy, role-based access control (RBAC), and policy compliance.
- Cost-neutral operation: Grouping subscriptions or defining custom tags does not alter the underlying cost of provisioned resources.
- Indirect cost control: While policies can restrict expensive VM sizes from being deployed, the policy itself is not a billed cost driver.
This Answer Would Be Correct If
A scenario asked which structural constructs and governance frameworks are used to organize Azure subscriptions, enforce compliance rules, and define network boundaries without adding direct billing costs.
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
Azure Reservations Pricing Model
Compare cloud pricing models
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Reservations
Compare cloud pricing models
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Spot Virtual Machines
Compare cloud pricing models
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Hybrid Benefit
Compare cloud pricing models
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Pay-as-You-Go Pricing
Compare cloud pricing models
IntermediateAZ-400 Designing and Implementing Microsoft DevOps Solutions Exam
GitHub Branch Protection Rules and SAML SSO
Design and implement permissions and roles in GitHub
Last updated Validated