Free Microsoft Azure Fundamentals AZ-900 Practice Test

An Azure subscription is a logical container that organizes resources created in Azure. It acts as a boundary for billing by tracking resource usage and costs. This helps organizations manage expenses and resource allocations effectively. While access permissions are managed through Azure Active Directory and role-based access control and physical deployment locations are determined by Azure regions, the subscription itself is central to billing and resource management.

Azure Virtual Machines provide full control over the operating system, allowing the installation of custom drivers and software. This option gives administrators the ability to manage the underlying infrastructure, including maintenance, updates, and patches.

Azure Functions and Azure App Service remove the underlying infrastructure and do not offer such granular control over the operating system.

Azure Container Instances simplify container deployment without the need to manage virtual machines directly but do not provide direct access to the underlying operating system for installing custom components.

An Azure subscription represents a logical container where resources are deployed and managed. It acts as a billing unit; all resources that are deployed within the subscription are billed together under that subscription. It defines the boundary for resource management and usage. Subscriptions are linked to a specific Azure account and are used to group usage and billing data. A management group, on the other hand, is a collection of multiple subscriptions, and an Azure account is an identity that has access to Azure. Understanding the purpose and boundaries of a subscription helps manage costs, resources, and governance effectively.

False. Azure Service Health provides personalized alerts and guidance when Azure service issues, planned maintenance, or other changes affect your Azure resources. It does not monitor the performance metrics of your applications. Monitoring application performance is a function of Azure Monitor.

Azure Service Health is the appropriate tool for setting up personalized alerts about service issues and planned maintenance that could impact your services. It provides a customizable dashboard and alerting system specifically designed to notify administrators about Azure service problems in regions and services they are using.

Azure Monitor focuses on collecting, analyzing, and acting on telemetry from your cloud and on-premises environments but does not provide notifications about Azure service outages.

Azure Advisor offers recommendations to help improve the performance, security, and reliability of your Azure resources but does not send alerts about service issues. Azure Resource Health gives information about the health of individual resources, helping to diagnose and support when resources are unavailable, but it does not alert you to broader service incidents or maintenance events.

The pay-as-you-go pricing model charges customers based on actual resource usage without requiring upfront payments or long-term commitments. This model provides flexibility and is ideal for organizations that want to avoid initial expenditures and pay only for what they use. Reserved Instances require a commitment over a period, typically offering discounts in exchange for upfront payment, which doesn't meet the organization's need to avoid upfront costs and commitments. Spot pricing offers discounted rates for unused capacity but comes with the risk of service interruption, which may not be suitable for all workloads. Enterprise Agreements involve contractual commitments and often upfront negotiations, which contrasts with the organization's desire for flexibility and no upfront costs.

Azure Cloud Shell is a browser-based scripting environment that allows users to manage their Azure resources using either Bash or PowerShell. It offers the built-in capability to execute scripts like those written for Azure Resource Manager (ARM) without the need for any additional installation or configuration on a local machine. Azure Portal, while it does facilitate management of Azure resources, it is not a scripting environment. Azure Advisor, conversely, provides recommendations on best practices but doesn't perform deployments. Azure Bash isn't a valid Azure feature; it's possibly a confusion with the Bash environment available in the Cloud Shell.

Azure File Sync synchronizes files between on-premises Windows Servers and Azure, ensuring data is consistent and up-to-date across both locations. It is designed for scenarios requiring ongoing synchronization.

AzCopy is a command-line tool for transferring data to and from Azure Storage but does not support continuous synchronization.

Azure Storage Explorer provides a graphical interface for managing Azure Storage but lacks synchronization capabilities.

Azure Data Factory is used for data integration and movement but is not intended for file synchronization between servers and Azure Storage.

Software as a Service (SaaS) is a cloud computing offering that provides users with access to a vendor's cloud-based software. Users do not install applications on their local devices. Instead, the applications run on cloud-based servers, and users access the software via the web or an API. The vendor manages the infrastructure, middleware, application software, and application data. An example of a SaaS application is a web-based email service through which you can send and receive emails without having to manage the email server or client software. In contrast, the other options listed either fall under different service models, such as PaaS (where the environment, but not the applications, is managed by the provider) and IaaS (which provides virtualized computing resources over the internet), or are not related to cloud service models at all.

Conditional Access in Microsoft Entra allows administrators to create policies that provide or block access to resources based on real-time conditions like user risk, device compliance status, and location. This feature enhances security by ensuring that access is granted only when specified conditions are met.

Multi-Factor Authentication (MFA) adds an extra layer of authentication but does not offer policy-based controls based on real-time signals.

Privileged Identity Management focuses on managing and monitoring access to privileged roles, not on dynamic access policies.

Access Reviews are used to periodically reevaluate user access permissions but do not enforce access based on real-time conditions.

Choosing smaller VM sizes with less CPU and memory resources directly reduces compute costs because pricing is based on the resources allocated. Deploying VMs in the region closest to users may improve performance but doesn't necessarily lower costs unless that region has reduced pricing. Assigning tags helps with cost tracking and management but does not reduce the actual costs. Using the Azure Pricing Calculator assists in estimating costs but doesn't reduce them; it's a planning tool.

Azure Monitor alerts can be used to set up automated notifications based on metric criteria. In this case, an alert on the processor time metric exceeding the 80% threshold for a sustained period (10 minutes) can be configured through Azure Monitor. Although Log Analytics is part of Azure Monitor and is used for querying and analyzing log files, it isn't directly responsible for setting up alerts. Application Insights is focused on application performance monitoring and would be used if you were specifically interested in the performance metrics of web applications. Azure Automation can help automate cloud management tasks but is not the service designed for setting up performance alerts.

Platform as a Service (PaaS) is the appropriate cloud service type in this scenario. It allows developers to focus on building and deploying applications without the need to manage the underlying infrastructure such as servers, storage, or operating systems. PaaS provides the necessary development tools and services, enabling the company to deploy and manage their applications efficiently. Infrastructure as a Service (IaaS) requires managing operating systems and servers, which the company wants to avoid. Software as a Service (SaaS) provides fully managed applications and does not allow for deploying custom applications.

Platform as a Service (PaaS) is the correct answer because it provides a platform allowing customers to develop, run, and manage applications without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app. It abstracts much of the system administration effort needed for setting up environments and lets developers focus on writing code. Infrastructure as a Service (IaaS) would not be the ideal choice here because it does provide the virtualized hardware but would still require the company to manage the servers and software stack. Software as a Service (SaaS) is also not correct because it offers completed products to end-users, which does not align with the company's goal of developing a custom application. Desktop as a Service (DaaS) is incorrect because it mainly provides virtual desktop environments, not a development platform.

This statement is not correct. While cloud services greatly enhance the reliability and availability of applications, they do not provide 100% guaranteed uptime. Service Level Agreements (SLAs) provided by cloud vendors typically include commitment to high availability but not absolute perfection. Therefore, organizations still need to have disaster recovery plans in place to prepare for the rare instances when disruptions may occur.