Exam: AZ-900: Microsoft Azure Fundamentals

A. Yes
✅ Explanation:
The Professional Direct support plan does include architecture guidance, including assessments of Azure environment designs, which is what the company is seeking. It offers faster response times and access to ProDirect Delivery Managers, which help provide proactive guidance.
While Standard support offers technical support, it does not provide this level of design assessment. Therefore, Professional Direct is the lowest-cost plan that meets this requirement.

B. No
✅ Explanation:
Deploying Azure Virtual Machines (VMs) is an example of using Infrastructure as a Service (IaaS), not Platform as a Service (PaaS).
IaaS provides virtualized computing resources over the internet, such as virtual machines, networking, and storage — all of which are managed by the user.
PaaS, on the other hand, abstracts away the infrastructure layer and provides a platform to develop and deploy applications without managing the underlying servers or VMs.

A. Yes
✅ Explanation:
- Deploying Azure Virtual Machines (VMs) is a classic use case of Infrastructure as a Service (IaaS).
- IaaS provides the basic building blocks for cloud IT: virtual machines, storage, networking, and operating systems.
- With IaaS, you manage the VM, OS, and apps, while Azure manages the physical infrastructure.

A. Standard
Explanation:
Custom domains →
✅ Supported in Basic and Standard (not in Free or Shared).
10 GB storage per app →
✅ Standard provides enough storage.
❌ Basic might be tight, as storage is more limited compared to Standard.
❌ Free/Shared are too limited.
Dedicated compute instances →
✅ Basic and Standard provide dedicated compute.
❌ Free/Shared do not offer dedicated compute.
Built-in load balancing between instances →
✅ Only Standard supports auto-scaling and load balancing.
❌ Basic supports manual scaling but not load balancing.
Costs must be minimized →
While Basic is cheaper, it does not meet the load balancing requirement.
Standard is the lowest-cost plan that meets all the requirements.

Answer: B
✅ Explanation:
Why this solution does NOT meet the goal:
- Multiple Azure AD directories mean separate user accounts, roles, policies, and access management for each directory.
- Users can’t be easily assigned roles or access across directories.
-It increases complexity, overhead, and cost.
✅ The better approach:
- Use Management Groups, Subscriptions, Resource Groups, and Role-Based Access Control (RBAC) within a single Azure AD directory:
- Create separate subscriptions or resource groups for each division.
- Use RBAC to assign each division’s admin appropriate permissions within the same Azure AD tenant.
- This keeps the environment segmented but easy to manage.

Answer:B
✅ Explanation:
Custom domain (miami.weyland.com)
Supported in Basic and Standard
❌ Not supported in Free or Shared
Deployment to two instances
Basic supports manual scaling to multiple instances
Standard supports auto-scaling
❌ Free and Shared do not support scaling to multiple instances
SSL support
Basic and Standard support SSL (SNI SSL)
❌ Free and Shared have limited or no support for custom SSL
12 GB of storage
Basic offers up to 50 GB shared across apps
✅ So this meets the 12 GB requirement
Costs must be minimized
Basic is cheaper than Standard and meets all requirements
✅ Best cost-effective option

Answer:A
✅ Explanation:
The elastic expenditure model refers to a pay-as-you-go pricing model, where you only pay for the computing resources you use. This is exactly what Azure offers with its pay-as-you-go subscription.
In this case:
- The company is migrating VMs from an on-premises Hyper-V setup.
- They plan to use an Azure pay-as-you-go subscription.
- This model automatically scales costs with usage — a key characteristic of an elastic expenditure model.

Answer:B
✅ Explanation:
There is no official expenditure model in Azure called the "scalable expenditure model". The correct and commonly used term for Azure's billing approach under a pay-as-you-go subscription is the elastic expenditure model.

Answer: A
✅ Explanation:
- Operational Expenditure (OpEx) refers to ongoing costs for running a service or product.
- Capital Expenditure (CapEx) refers to one-time, upfront costs, like buying servers.
- Migrating virtual machines to an Azure pay-as-you-go subscription is OpEx, because you are paying monthly based on usage, not buying hardware.