Microsoft Azure Fundamentals Practice Test (AZ-900)

Azure Service Health is the tool designed to keep you informed about the health of Azure services and regions that you use. It offers a personalized view of ongoing incidents, planned maintenance, and health advisories and lets you set up alerts so you are notified through email, SMS, or other channels. It does not collect or display performance metrics from your applications. Azure Monitor and its Application Insights feature handle application-level telemetry, and Azure Advisor offers best-practice recommendations rather than health alerts.

The correct statement is that Availability Zones are physically separate datacenters within an Azure region. They are equipped with independent power, cooling, and networking to protect applications and data from datacenter-level failures. Virtual network segments are used for network isolation, not physical high availability. Two or more regions paired for disaster recovery describes region pairs. A logical grouping of VMs within one datacenter describes an Availability Set.

Zone-Redundant Storage replicates data synchronously across multiple facilities within one region, protecting against the failure of any single data center without the latency associated with cross-region replication.

Locally Redundant Storage keeps multiple copies of data within a single facility, which doesn't protect against data center failure.

Geo-Redundant Storage replicates data to a secondary region, introducing latency that the company wants to avoid.

Read-Access Geo-Redundant Storage provides read access to data in a secondary region but still involves cross-region replication.

Azure Functions is a serverless compute service that allows you to run event-triggered code without having to explicitly provision or manage infrastructure. It automatically scales based on demand and you are charged only for the compute resources used during the execution of your functions. Virtual Machines require management of the underlying infrastructure, whereas container services like Azure Kubernetes Service (AKS) also involve orchestration. Logic Apps, although used for automated workflows, are not primarily compute services and do not offer the same kind of execution model.

Microsoft Purview provides a unified data governance solution that allows organizations to discover, classify, and manage data across on-premises, multi-cloud, and SaaS sources. It helps create a holistic map of data assets, enabling better data governance and compliance. Other services like Azure Policy focus on enforcing organizational standards and assessing compliance for resources, Azure Monitor is used for collecting and analyzing telemetry data to maximize performance, and Azure Security Center enhances security posture and provides threat protection, but they do not offer unified data governance capabilities.

Azure Advisor provides personalized recommendations to help optimize Azure resources in terms of availability, security, performance, and cost. It analyzes resource configurations and usage data to offer actionable solutions.

Azure Monitor collects and analyzes data but does not provide recommendations.

Azure Policy helps enforce rules for compliance but doesn't offer optimization advice.

Azure Service Health informs about service issues but doesn't give improvement suggestions.

Azure Cost Management provides tools for monitoring and controlling Azure spending. It allows users to set budgets, view cost analyses, and optimize cloud costs. Azure Monitor is used for collecting metrics and logs from resources, Azure Advisor provides recommendations for best practices, and Azure Security Center focuses on security posture, not cost management.

Public cloud is delivered by a third-party provider that owns and manages the underlying infrastructure. Customers access resources over the internet and are billed according to actual usage, eliminating the need for significant capital investment. Private clouds, hybrid clouds, and traditional on-premises virtualization all require the organization to purchase or maintain some portion of the hardware, leading to higher upfront costs and less consumption-based billing.

Platform as a Service (PaaS) is the correct choice 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. This model enables companies to focus on the development of their applications by using pre-built tools provided by the cloud service, without worrying about the underlying servers, storage, or network.

Azure Functions is the most appropriate service for this scenario as it allows developers to execute code in response to various triggers, such as the uploading of images to a storage container, without the hassle of managing infrastructure. It automatically scales the execution to match the demand and you incur costs only when your functions are running. Azure Event Grid is an event-routing service that could help trigger the function execution but, by itself, does not handle code execution. Azure Container Instances (ACI) can quickly run containers without requiring server management but it's not inherently serverless and lacks the automatic scaling based on events. Azure Automation primarily targets automation of cloud management tasks rather than being a serverless platform for running custom code in response to events.

Infrastructure as a Service (IaaS) provides virtualized computing resources over the internet. It allows the company to have full control over the operating system, installed software, server configurations, and network settings. IaaS is suitable when you need to manage and control the underlying infrastructure but want to avoid the costs and complexities of purchasing and managing physical servers. In contrast, Platform as a Service (PaaS) abstracts away the underlying infrastructure and limits control over the operating system, while Software as a Service (SaaS) provides fully managed applications without any control over the infrastructure or platform.

Using tags allows the administrator to assign custom metadata to Azure resources in the form of key-value pairs. This enables categorization and better organization of resources, facilitating cost tracking and management across different departments or projects.

Resource groups group resources that share the same lifecycle but do not provide a way to assign custom metadata for categorization. Azure Policies are used to enforce rules and ensure compliance but do not assist in categorizing resources. Role-Based Access Control manages user permissions and access to resources, not resource categorization.

Conditional Access in Microsoft Entra ID enables organizations to create policies that control user access based on various signals like location, device compliance, and risk detection. By using Conditional Access, the company can ensure that access to resources is granted only when specific conditions are met.

Privileged Identity Management manages and monitors access to privileged roles but doesn't enforce access policies based on signals.

Azure Information Protection classifies and protects documents and emails, not user access.

Multi-Factor Authentication (MFA) adds an extra layer of security but doesn't provide dynamic access controls based on factors like location or device compliance.

Azure Subscriptions are the right choice for the company as they form the container for billing, access control, and resource allocation. Each department can have its own subscription, with the costs separated per subscription. Management groups are not the answer as they are used to manage access, policies, and compliance across multiple subscriptions, rather than separating the billing and access control for different departments. A single subscription with multiple resource groups would not ideally segregate the billing by department. While Azure Active Directory performs identity and access management, it doesn't separate resources and billing at the departmental level.

Azure Resource Manager (ARM) templates allow you to define your infrastructure and configurations using declarative JSON syntax. This enables you to automate deployments and maintain consistency across environments.

Azure Portal is a graphical interface and isn't suitable for automating deployments through code.

Azure Advisor provides personalized recommendations to optimize your resources but doesn't facilitate deployment automation.

Azure Monitor is used for collecting and analyzing telemetry data, not for deploying resources.