Use VCE Exam Simulator to open VCE files

AZ-900 Microsoft Practice Test Questions and Exam Dumps
Your company has data centers in Los Angeles and New York. The company has a Microsoft Azure subscription. You are configuring the two data centers as geo-clustered sites for site resiliency. You need to recommend an Azure storage redundancy option.
You have the following data storage requirements:
Data must be stored on multiple nodes.
Data must be stored on nodes in separate geographic locations.
Data can be read from the secondary location as well as from the primary location.
Which of the following Azure storage redundancy options should you recommend?
A. Geo-redundant storage
B. Read-only geo-redundant storage
C. Zone-redundant storage
D. Locally redundant storage
Azure provides several storage redundancy options to ensure high availability and data durability across various scenarios. The best option for your requirements depends on the geographic distribution of the data, the need for resiliency, and whether data should be readable from the secondary location.
Here is an overview of the relevant Azure storage redundancy options and why Geo-redundant storage (GRS) is the best choice for your scenario:
Option A: Geo-redundant storage (GRS) (Correct)
Geo-redundant storage (GRS) ensures that your data is replicated to a secondary geographic region. This option provides both resiliency and disaster recovery, as it stores the data in two different geographic locations, ensuring availability even if one region experiences an outage.GRS is a great fit because it meets all your requirements:
Data is stored on multiple nodes across two geographically separate locations.
Data can be read from both the primary and secondary locations, ensuring continued access to data even if one region faces issues.
GRS replicates your data asynchronously to a secondary region, which aligns perfectly with your need for geo-clustered sites with the ability to read data from either site.
Option B: Read-only geo-redundant storage (RA-GRS) (Incorrect)
RA-GRS is similar to GRS but with the key difference that the secondary replica is read-only. While it provides resiliency and geographic redundancy, it restricts writes to the secondary region, making it unsuitable if you need to actively read and write to both sites. In your case, you want the ability to read data from both the primary and secondary locations, so RA-GRS wouldn’t be the ideal choice.
Option C: Zone-redundant storage (ZRS) (Incorrect)
Zone-redundant storage (ZRS) stores copies of data in different availability zones within the same region, ensuring high availability within that region. However, ZRS does not meet the geographic redundancy requirement for your scenario, as it does not replicate data across regions. Therefore, it wouldn’t provide the necessary resiliency between your Los Angeles and New York data centers.
Option D: Locally redundant storage (LRS) (Incorrect)
Locally redundant storage (LRS) replicates data within a single region, typically across three availability zones, but it doesn’t provide cross-region replication. While it provides high availability within a region, it doesn’t meet your need for geographical redundancy or the ability to read data from multiple locations.
Given your requirements for geographic redundancy, resiliency, and the ability to read data from both locations, Geo-redundant storage (GRS) is the best choice for your Azure storage redundancy needs. It ensures that your data is safely stored across geographically separated locations, with full read and write access from both regions.
Question No 2:
Your company's Azure subscription includes a Basic support plan. They would like to request an assessment of an Azure environment's design from Microsoft. This service, however, is not supported by the existing plan.
You want to ensure that the company subscribes to a support plan that allows this functionality while keeping expenses to a minimum.
You recommend that the company subscribes to the Professional Direct support plan. Does the solution meet the goal?
A. Yes
B. No
When choosing an Azure support plan, it is essential to align the plan's features with the specific requirements of the company. In this scenario, the company requires the ability to request an assessment of their Azure environment's design, which is typically considered an advanced support service. Let's analyze the options in detail.
Basic Support Plan:
The Basic support plan is the default and free support plan provided with every Azure subscription. It offers only limited support, such as access to documentation, community forums, and the ability to submit a billing and subscription issue. It does not provide direct access to Microsoft support engineers for assessments or more detailed advisory services.
Professional Direct Support Plan:
The Professional Direct plan provides more advanced support, including access to faster response times and 24/7 access to technical support. However, it does not include the ability to request an in-depth environment design assessment, which is typically part of the Azure Advisory Services available in higher-tier plans such as the Premier support plan.
Although the Professional Direct plan includes enhanced support, it does not provide the same level of advisory services as the Premier support plan, which is where such assessments are typically available.
Premier Support Plan:
The Premier support plan offers full access to Azure environment design assessments, technical reviews, and other consulting services. This plan is designed for organizations with high-level support needs, including proactive assessments and tailored advice from Microsoft.
Why Professional Direct Does Not Meet the Goal:
The requirement for an Azure environment's design assessment typically falls under Advisory Services that are part of the Premier Support Plan. The Professional Direct plan, although offering more advanced support, does not provide access to these advisory services. Therefore, recommending the Professional Direct support plan would not meet the goal of gaining access to Microsoft’s design assessment service.
While the Professional Direct support plan offers significant improvements over the Basic plan, it does not cover the specific need for an Azure environment design assessment. To meet the goal, the company would need to subscribe to the Premier Support Plan, which includes these higher-level advisory services.
Thus, the solution does not meet the goal, and the correct answer is B. No.
Question No 3:
You are tasked with deploying Azure virtual machines for your company. You need to make use of the appropriate cloud deployment solution.
You should make use of Software as a Service (SaaS). Does the solution meet the goal?
A. Yes
B. No
To understand whether the solution is appropriate, it is important to first review the different types of cloud service models and their respective use cases, especially in relation to the deployment of Azure virtual machines (VMs).
SaaS refers to cloud-based software applications that are fully managed by the service provider. Users access the software over the internet, typically through a web browser, without needing to worry about infrastructure or underlying software maintenance.Examples of SaaS include applications like Microsoft Office 365, Salesforce, and Google Workspace.
These services provide pre-configured solutions, but they do not provide direct control over the underlying infrastructure or virtual machines.In the context of deploying Azure virtual machines, SaaS would not be the appropriate solution, as it does not provide the ability to manage or deploy virtual machines directly. Instead, SaaS provides complete applications managed by the provider, not customizable computing resources.
PaaS provides a platform that allows developers to build, deploy, and manage applications without worrying about the underlying infrastructure. While PaaS offers more control over the application layer compared to SaaS, it still abstracts much of the underlying infrastructure management.Azure offers several PaaS services, such as Azure App Services, which provide environments for hosting web apps without managing virtual machines directly.
However, PaaS would still not give you full control over virtual machines as required in this case.IaaS provides virtualized computing resources over the internet, including virtual machines, storage, and networking components. Azure's Virtual Machines (VMs) fall under IaaS, where users have full control over the virtual machines, including their configuration, operating system, and software.
For this specific scenario, where you need to deploy Azure virtual machines, IaaS would be the appropriate solution, as it gives you direct control over the VM infrastructure.
The task involves deploying virtual machines, which requires direct control over the infrastructure, including configuring the operating systems and software on the VMs. SaaS does not offer this level of control over computing resources. Instead, SaaS provides complete, ready-made applications that are managed by the service provider. Therefore, SaaS is not suitable for deploying virtual machines.
To deploy Azure virtual machines, you need to use Infrastructure as a Service (IaaS), not SaaS. The correct answer is B. No.
Question No 4:
You are tasked with deploying Azure virtual machines for your company. You need to make use of the appropriate cloud deployment solution.
You should make use of Platform as a Service (PaaS). Does the solution meet the goal?
A. Yes
B. No
Answer: B. No
To determine if the solution of using Platform as a Service (PaaS) is appropriate for deploying Azure virtual machines, let's first review the different cloud service models and their specific use cases.
PaaS provides a platform that allows developers to build, deploy, and manage applications without worrying about the underlying hardware or operating systems. PaaS services handle most of the infrastructure management tasks, such as networking, storage, and compute resources, but still allow users to focus on developing applications.
Examples of PaaS offerings in Azure include Azure App Service (for hosting web apps), Azure Functions (for serverless compute), and Azure SQL Database (for managed database services).
PaaS abstracts away much of the infrastructure management, which means users cannot directly manage virtual machines or their configurations. PaaS is ideal for application hosting where developers need to focus on code, not the virtual machines or the underlying server infrastructure.
IaaS provides more control over virtual machines (VMs), networking, and storage. It is a more flexible and customizable cloud service model where users have the ability to configure and manage their virtual machines and other infrastructure resources directly.
In Azure, Azure Virtual Machines (VMs) are an example of IaaS. Users can deploy and manage VMs with complete control over the operating system, configuration, and installed applications.
IaaS is the correct solution when you need to deploy and manage virtual machines directly, as it allows you full control over the computer infrastructure, unlike PaaS, which abstracts these components away.
SaaS delivers fully managed software applications to users, with no need for managing underlying infrastructure. It is not suited for deploying virtual machines.Examples include services like Microsoft Office 365 or Salesforce.
The solution provided, Platform as a Service (PaaS), does not meet the goal of deploying Azure virtual machines. PaaS is best suited for application hosting, where you don't need to manage virtual machines directly. For deploying and managing Azure VMs, the appropriate service model is Infrastructure as a Service (IaaS), which gives you control over the virtual machines.
Since PaaS abstracts the underlying infrastructure and doesn't allow direct management of virtual machines, it is not suitable for the task of deploying Azure virtual machines. The correct answer is B. No.
You are tasked with deploying Azure virtual machines for your company. You need to make use of the appropriate cloud deployment solution.
You should make use of Infrastructure as a Service (IaaS). Does the solution meet the goal?
A. Yes
B. No
To understand why Infrastructure as a Service (IaaS) is the appropriate cloud deployment solution for deploying Azure virtual machines, it's essential to understand the characteristics and use cases of different cloud service models.
Infrastructure as a Service (IaaS) is a cloud computing model that provides virtualized computing resources over the internet. In IaaS, users are responsible for managing the operating system, applications, and data, while the cloud provider manages the physical infrastructure, including servers, storage, and networking.
When deploying Azure Virtual Machines (VMs), IaaS is the most suitable choice. The Azure VM service provides users with full control over the virtual machines, including the ability to install software, configure the OS, and manage the virtual infrastructure. With IaaS, you can deploy highly flexible and scalable virtual machines on demand, making it the ideal solution for businesses that require specific configurations, performance levels, and customization of their virtualized resources.
Full Control: With IaaS, users have complete control over their virtual machines, including the operating system and configuration.
Scalability: You can scale resources up or down based on demand, ensuring that your infrastructure aligns with your workload needs.
Cost Efficiency: With IaaS, you only pay for what you use, and you can optimize costs by resizing VMs or leveraging reserved instances for long-term savings.
Flexibility: IaaS allows you to choose the right size and type of VM based on specific workload requirements.
Since the task involves deploying virtual machines in Azure, IaaS is the correct cloud deployment model. PaaS and SaaS are not appropriate, as they abstract away the underlying infrastructure and focus on application hosting or providing software solutions, which do not offer the level of control required for managing VMs.
Therefore, the solution of using IaaS for deploying Azure VMs fully meets the goal, making A. Yes, the correct answer.
Your developers have created 10 web applications that must be hosted on Azure. You need to determine which Azure web tier plan to host the web apps. The web tier plan must meet the following requirements:
The web apps will use custom domains.
The web apps each require 10 GB of storage.
The web apps must each run in dedicated compute instances.
Load balancing between instances must be included.
Costs must be minimized.
Which web tier plan should you use?
A. Standard
B. Basic
C. Free
D. Shared
When selecting an Azure Web App plan that meets specific requirements for hosting multiple web applications, it is essential to understand the various pricing tiers and their features. Let's evaluate each option based on the given requirements.
This tier provides limited resources and is intended for testing and experimentation, not production workloads. It offers only 1 GB of storage and does not support custom domains, dedicated compute instances, or load balancing.
Not suitable because it does not meet the requirement for custom domains or dedicated compute instances.
The Shared tier allows multiple apps to share resources, meaning they don't run on dedicated compute instances. This tier does not support custom domains, load balancing, or isolation between apps, making it unsuitable for production environments that require dedicated resources and scalability.
Not suitable because it doesn’t meet the requirements for dedicated compute or load balancing.
The Basic tier provides dedicated compute instances for the web apps, and supports custom domains and load balancing. However, it is limited in features such as scaling, and it provides only 10 GB of storage per app, which aligns with the storage requirement. The Basic plan may be sufficient for simple applications but lacks some advanced features like autoscaling.
Suitable but doesn't provide scaling features or additional advanced capabilities that may be required in a growing production environment.
The Standard tier is the best choice for production environments with dedicated compute instances, custom domain support, and load balancing across instances. This tier also supports autoscaling, which means the web apps can scale up or down based on demand. It provides 50 GB of storage per app, more than the required 10 GB.
Most suitable because it meets all the requirements: custom domains, dedicated compute instances, storage, load balancing, and scalability.
The Standard tier (A) is the most appropriate plan for hosting web applications with dedicated compute, custom domains, load balancing, and sufficient storage. It also offers autoscaling for future growth, making it the best solution to meet the company's requirements while minimizing costs effectively. Therefore, the correct answer is A. Standard.
You are planning to migrate a company to Azure. Each of the company's numerous divisions will have an administrator in place to manage the Azure resources used by their respective division. You want to ensure that the Azure deployment you employ allows for Azure to be segmented for the divisions, while keeping administrative effort to a minimum.
Solution: You plan to make use of several Azure Active Directory (Azure AD) directories.
Does the solution meet the goal?
A. Yes
B. No
The objective is to segment Azure resources across divisions while minimizing administrative effort. Let's break down why using multiple Azure AD directories is not the ideal solution for this case.
Azure AD directories are used for identity and access management across Azure resources. Each directory can hold its own set of users, groups, and applications. When considering an approach with multiple Azure AD directories, each directory would be separate and independent, which complicates the management of user identities and access across the different divisions of the company.
Segmentation of Resources: While Azure AD directories can be used to manage users and access, they do not inherently provide the segmentation of Azure resources such as virtual machines, storage, or networking across divisions. Azure resources are typically managed within subscriptions, and resource groups provide the natural way to segment resources within a single Azure AD tenant.
Administrative Overhead: Managing multiple Azure AD directories increases complexity and administrative overhead. Each directory would require its own set of administrators and maintenance, making cross-division management more cumbersome. Managing user access across multiple directories also requires handling cross-directory authentication, adding more complexity and reducing the simplicity that the solution aims to achieve.
The ideal approach to segmenting Azure resources for different divisions with minimal administrative effort is to use Azure subscriptions and resource groups. You can create a separate subscription for each division or group related resources within resource groups within the same Azure AD tenant. This allows you to control access and resources for each division while using Azure RBAC (Role-Based Access Control) to minimize administrative overhead.
In conclusion, using several Azure AD directories would not meet the goal of segmenting Azure resources for each division with minimal administrative effort. The correct approach would be to use Azure subscriptions and resource groups, which would better meet the requirements of the scenario. Therefore, the correct answer is B. No.
Your developers have created a portal web app for users in the Miami branch office. The web app will be publicly accessible and used by the Miami users to retrieve customer and product information. The web app is currently running in an on-premises test environment. You plan to host the web app on Azure.
Which Azure web tier plan to host the web app. The web tier plan must meet the following requirements:
The website will use the miami.weyland.com URL.
The website will be deployed to two instances.
SSL support must be included.
The website requires 12 GB of storage.
Costs must be minimized.
Which web tier plan should you use?
A. Standard
B. Basic
C. Free
D. Shared
To determine the correct Azure Web App tier, let’s evaluate each of the available options based on the given requirements.
Custom Domain: The website will use a custom URL (miami.weyland.com).
Two Instances: The app will run in two instances, indicating a need for high availability.
SSL Support: The app needs SSL support for secure connections.
12 GB of Storage: The app needs sufficient storage for its content.
Cost Efficiency: Costs must be minimized.
This tier provides basic capabilities for small, non-production apps. It does not support custom domains, SSL, or scaling across multiple instances. Additionally, it provides only 1 GB of storage, which is insufficient for the 12 GB requirement.Not suitable because it lacks the necessary features like custom domains, SSL, and sufficient storage.
The Shared tier allows multiple apps to share resources, which limits performance and flexibility. It does not provide custom domain support, SSL, or load balancing across instances.Not suitable because it doesn't support custom domains or SSL and lacks the flexibility to meet the other requirements.
The Basic tier allows dedicated compute resources for web apps and supports custom domains and SSL. However, it only provides 10 GB of storage per app, which is slightly less than the required 12 GB. Additionally, while it does support scaling to multiple instances, it lacks features like autoscaling.Suitable but not ideal because it doesn’t provide enough storage.
The Standard tier is the best fit for this use case. It supports custom domains, SSL, and scaling to multiple instances. The Standard tier provides 50 GB of storage, which easily exceeds the 12 GB requirement, ensuring ample space for future growth. Additionally, it supports autoscaling, load balancing, and more advanced features like staging environments and traffic routing.
Ideal because it meets all the requirements: custom domains, SSL support, storage, and scalability, while remaining cost-effective for production environments.
The Standard tier (A) is the most appropriate plan for hosting the web app. It meets all the requirements for custom domains, SSL, sufficient storage, and scalability. The Basic tier falls short on storage, and both the Free and Shared tiers are insufficient for production workloads with custom domain and SSL support. Therefore, the correct answer is A. Standard.
Your company is planning to migrate all their virtual machines to an Azure pay-as-you-go subscription. The virtual machines are currently hosted on the Hyper-V hosts in a data center. You are required to make sure that the intended Azure solution uses the correct expenditure model.
Solution: You should recommend the use of the elastic expenditure model.
Does the solution meet the goal?
A. Yes
B. No
When planning the migration of virtual machines (VMs) to Azure, selecting the correct expenditure model is critical to ensure cost efficiency and proper budgeting. In this scenario, the recommendation is to use the elastic expenditure model, but let’s analyze if this is the best choice.
The Pay-as-you-go model is the most flexible and common expenditure model for Azure services. In this model, customers are billed based on actual usage (per minute or per hour), and there are no upfront costs or long-term commitments. This allows companies to scale their services up or down as needed, making it ideal for unpredictable workloads.
Reserved Instances offer a more predictable cost model where customers commit to a certain amount of usage for a one- or three-year period in exchange for a significant discount compared to the PAYG model. This is useful for workloads with predictable usage patterns, such as virtual machines that will run 24/7.
The elastic expenditure model generally refers to a model where resources are automatically scaled up or down based on demand, and the pricing adjusts accordingly. While this model can apply in some cases, it is more commonly associated with serverless services (such as Azure Functions) or auto-scaling in cloud services rather than being a general expenditure model for VMs.
The elastic expenditure model is often more applicable to serverless or auto-scaling services where the resources adjust dynamically based on demand. For virtual machines, the Pay-as-you-go (PAYG) or Reserved Instances models are more appropriate. Since the company is migrating VMs, a Pay-as-you-go model would give flexibility, or Reserved Instances could be recommended if workloads are predictable.
Therefore, the elastic expenditure model is not the most appropriate model for virtual machines, making B. No the correct answer. Pay-as-you-go would be the better solution for this scenario.
Top Training Courses
LIMITED OFFER: GET 30% Discount
This is ONE TIME OFFER
A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.
Download Free Demo of VCE Exam Simulator
Experience Avanset VCE Exam Simulator for yourself.
Simply submit your e-mail address below to get started with our interactive software demo of your free trial.