Microsoft Practice Questions, Discussions & Exam Topics by our Authors
You have an Azure virtual machine that is monitored by using Azure Monitor. The virtual machine has the Azure Log Analytics agent installed. You plan to deploy the Service Map solution from the Azure Market...To support the Service Map solution from the Azure Marketplace, you need to deploy an agent that enables the monitoring of dependencies and services running on your virtual machine. Let's analyze the available options: Option Analysis: 1. The Dependency Agent (A): - Description: The Dependency Agent is required for the Service Map solution. It collects data about network dependencies, such as processes, servers, and other services that are communicating with the virtual machine. This data is essential for Service Map to display dependencies and connections between systems in your environment. - Why It’s Ideal: Service Map relies on the Dependency Agent to map the relationships and communication between processes and services on your virtual machine. Without the Dependency Agent, the Service Map will not have the data it needs to track dependencies. - Scenario Use: This is the correct and necessary agent for enabling Service Map. If you plan to visualize and understand dependencies between processes on your virtual machine and others, this is the right choice. 2. The Telegraf Agent (B): - Description: The Telegraf agent is primarily used for collecting performance and metric data from different sources, including system metrics and logs. It is part of the Azure Monitor for Containers and can be used with Prometheus and InfluxDB. - Why It’s Not Ideal: The Telegraf agent is not specifically designed to support the Service Map solution. While it can collect useful system metrics, it does not provide the service dependency mapping that Service Map requires. - Scenario Use: This agent is useful for metrics collection but is not necessary for the ... Author: Rahul · Last updated May 25, 2026 |
HOTSPOT - You have a project in Azure DevOps that contains a Continuous Integration/Continuous Deployment (CI/CD) pipeline. You need to enable detailed logging by defining a pipeline variable. How should you configure the variable? To answer, sel...Author: Leo · Last updated May 25, 2026 |
You build an iOS app. You receive crash reports from Crashlytics. You need to capture the following data: * Crash-free users ...To capture crash-free users, custom events, and breadcrumbs in your iOS app, you need to set up the right services and frameworks. Let's break down each of the options: Option Analysis: 1. Configure the xcworkspace file in the project (A): - Description: The `.xcworkspace` file is used by Xcode to manage your workspace, especially when you're working with multiple targets or dependencies. However, configuring the workspace alone doesn’t directly address capturing crash-free users, custom events, or breadcrumbs. - Why It’s Not Ideal: The xcworkspace file is related to project organization but does not provide any specific functionality related to Crashlytics or other Firebase features that are required to capture crash-free users, custom events, or breadcrumbs. - Scenario Use: This option may be relevant for managing your project structure, but it doesn't help you capture the necessary data for this specific use case. 2. Add the GoogleAnalytics pod to the app (B): - Description: Google Analytics is a tool used for tracking user behavior and collecting analytics data. While Google Analytics can track events, it is not specifically designed for capturing crash reports, crash-free users, or breadcrumbs. - Why It’s Not Ideal: Google Analytics does not provide the detailed crash reporting and breadcrumb functionality that you need. It also doesn’t integrate with Crashlytics, which is the Firebase tool specifically designed for crash reports and related data. - Scenario Use: Google Analytics would be useful for general user behavior analytics but is not the appropriate choice for crash reporting and tracking crash-free users, custom events, and breadcrumbs. 3. Configure the Crashlytics pod in the app (C): - Description: Crashlytics is part of Firebase and is specifically designed to handle crash reports and related features. ... Author: Kunal · Last updated May 25, 2026 |
You have multiple teams that work on multiple projects in Azure DevOps. You need to plan and manage the consumers and producers for each project. The solution...In Azure DevOps, managing dependencies and providing an overview of multiple projects can be challenging when considering various teams, features, and user stories. The solution should focus on how to track relationships between projects while also ensuring visibility and manageability. Let's review each option: A) Add a Predecessor or Successor link to the feature or user story for the items of each project. - Predecessor and Successor links are typically used to track the order of work and dependencies between tasks. This approach could be helpful for understanding sequencing between user stories or features but might not be the most comprehensive way to track the overall consumers and producers for multiple projects. This doesn't provide an overview of all the projects or their interrelations in a centralized manner. - Limitations: This approach is good for specific task sequencing but may not show cross-project dependencies clearly, and doesn't facilitate a holistic view of multiple projects or consumers/producers at a higher level. B) Add a Parent or Child link to the feature or user story for the items of each project. - Parent and Child links are used to represent hierarchical relationships between work items, typically within the same project. It allows you to break down work (e.g., an epic into features or a feature into user stories). - Limitations: While this is useful for breaking down work within a project, it doesn't inherently represent dependencies between separate projects. You wouldn't be able to track inter-project relationships or dependencies (i.e., consumer and producer across projects) effectively with this approach. C) Install the Dependency Tracker extension and create dependencies for each project. - The Dependency Tracker extension in Azure DevOps is designed to help manage and visualize dependencies between work item... Author: Vivaan · Last updated May 25, 2026 |
DRAG DROP - You have a GitHub repository that contains the source code for an app named App1. You need to create process documentation for App1. The solution must include a diagram that displays the relationships between the phases of App1 as shown in the following exhibit. How should you complete the markdown code? To answer, drag the appropriate values to the correct targets. Each value m...Author: Scarlett · Last updated May 25, 2026 |
HOTSPOT - You have an Azure web app named webapp1 that uses the .NET Core runtime stack. You have an Azure Application Insights resource named AppInsights1 that collects telemetry data generated by webapp1. You plan to deploy webapp1 by using an Azure DevOps pipeline. You need to modify the sampling rate of the telemetry data processed by AppInsights1 without having to redeploy w...Author: Aditya · Last updated May 25, 2026 |
Your company has multiple microservices-based apps that use the following tracing libraries: * OpenTelemetry * OpenCensus * OpenTracing * Honeycomb * Jaeger The company purchases an Azure subscription and implements Application Insights in Azure Monitor. You plan to centralize distributed tracing for the apps. You need to identify which libraries can integrate directly wit...To centralize distributed tracing using Azure Application Insights, it's crucial to identify the libraries that can directly integrate with Application Insights for optimal tracing data collection and visualization. Let’s go over the libraries one by one: A) Honeycomb - Explanation: Honeycomb is a separate distributed tracing tool that focuses on observability and analytics. While Honeycomb provides powerful tracing capabilities, it doesn't integrate directly with Application Insights. Instead, it typically operates independently or with its own SDK. - Conclusion: Honeycomb cannot integrate directly with Azure Application Insights, making it not the right choice. B) OpenTracing - Explanation: OpenTracing is a vendor-neutral API standard for distributed tracing, but it does not have a direct integration with Azure Application Insights out of the box. To use OpenTracing with Application Insights, you would typically need a custom implementation or middleware to bridge OpenTracing with Application Insights. - Conclusion: OpenTracing is not directly integrated with Application Insights, so it's not the best option. C) Jaeger - Explanation: Jaeger is an open-source distributed tracing system, and while Application Insights has capabilities to ingest Jaeger trace data through an exporter, it doesn't natively integrate as seamlessly as some other libraries. Jaeger often needs additional setup or an intermediary service (like OpenTelemetry) to push its traces into Azure Application Insights. - ... Author: IronLion88 · Last updated May 25, 2026 |
You have an Azure web app named webapp1 that uses the .NET Core runtime stack. You have an Azure Application Insights resource named AppInsights1. Webapp1 sends telemetry data to AppInsights1. You need to en...To configure a fixed sampling rate for telemetry data sent by `webapp1` to `AppInsights1`, you need to manage the sampling behavior at the application level, not at the resource level in Azure Application Insights. Here's a breakdown of each option: A) From the code repository of webapp1, modify the ApplicationInsights.config file. - Explanation: The `ApplicationInsights.config` file is used primarily in the context of .NET Framework applications, not .NET Core. .NET Core applications, like `webapp1`, typically use code-based configuration for telemetry settings such as sampling. So, modifying this file would not apply to a .NET Core application. - Conclusion: This option is not applicable for .NET Core applications, so it is rejected. B) From the code repository of webapp1, modify the Startup.cs file. - Explanation: In .NET Core applications, the correct place to configure telemetry settings, including sampling, is in the `Startup.cs` file. You can modify the `ConfigureServices` method to configure the sampling rate using the `AddApplicationInsightsTelemetry` method with a custom `SamplingPercentage` or use a `TelemetryProcessor`. - How this works: This allows you to define a fixed sampling rate for telemetry data, meaning only a certain percentage of telemetry events will be sent to Application Insights. - Conclusion: This option is correct and the best way to implement a ... Author: Emily · Last updated May 25, 2026 |
DRAG DROP - You have an app named App1. You have a Log Analytics workspace named Workspace1 that contains two tables named Events and Logs. App1 manages events in multiple locations and writes logs to Workspace1. You need to query Workspace1 for all log entries related to Asia that occurred during the last two days. In which order should ...Author: Charlotte · Last updated May 25, 2026 |
DRAG DROP - You have a web app named App1 that uses Application Insights in Azure Monitor. You need to compare the hourly CPU usage of App1 from the last 24 hours. The solution must include a graph that has a threshold line at 75 percent. How should you complete the query? To answer, drag the appropriate values to the correct targets. Each value may be used onc...Author: Daniel · Last updated May 25, 2026 |
You use Azure Pipelines to build and deploy an app named App1. You plan to monitor App1 by using Application Insights. You create an Application Insights instance named AI...To configure your app `App1` to use the Application Insights instance `AI1` in Azure, you need to modify the correct configuration file in your application that integrates with Application Insights. Let's analyze each option in detail: A) appsettings.json - Explanation: The `appsettings.json` file is typically used in .NET Core applications to store configuration settings, including connection strings or other application-level settings. For Application Insights, you would typically store the Instrumentation Key or Connection String in `appsettings.json`. The file can be used to configure telemetry settings without modifying the source code directly. - How it fits: This file is appropriate for specifying settings such as the Instrumentation Key or Connection String for Application Insights in a .NET Core application. - Conclusion: This option is correct because it can store configuration data for Application Insights, specifically the Instrumentation Key or Connection String needed to link App1 to AI1. B) launchSettings.json - Explanation: The `launchSettings.json` file is used to configure settings related to how the app is run during development (like environment variables or application URLs). It is not used to store production settings like telemetry or the connection to Application Insights. - Conclusion: This file is used for local development settings and should not be used to configure Application Insights for production monitoring, so it is not the correct choice. C) startup.cs - Explanation: The `Startup.cs` file in an ASP.NET Core applicati... Author: Noah · Last updated May 25, 2026 |
HOTSPOT - You have an Azure virtual machine named web1. You need to query the amount of free memory that was available on web1 during the past seven days. The solution must meet the following requirements: * Display the data as a time chart. * Calculate the average value per hour. How should you co...Author: Benjamin · Last updated May 25, 2026 |
DRAG DROP - You have a web app named App1 that uses Application Insights in Azure Monitor to store log data. App1 has users in multiple locations. You need to query App1 requests from London and Paris that return a 404 error. The solution must meet the following requirements: * Return the timestamp url, resultCode, and duration fields * Only show requests made during the last...Author: Zara · Last updated May 25, 2026 |
DRAG DROP - You have a project in Azure DevOps. You need to configure a dashboard. The solution must include the following metrics: * Bottlenecks in the software development process * A burndown chart for the work in a single iteration * How long it takes to close a work item after the item was started Which type of widget should you use for each metric? To answer, drag the appropriate widget types to the correct metrics. Ea...Author: Vivaan · Last updated May 25, 2026 |
You have an Azure subscription that contains a Log Analytics workspace named WS1 and a virtual machine named VM1. You need to install the Microsoft Enterprise Cloud Monitoring extension on VM1. Which two values are required to configure the ex...When installing the Microsoft Enterprise Cloud Monitoring extension on a virtual machine (VM) in Azure, you need to configure certain values that allow the extension to connect the virtual machine to your Log Analytics workspace. Let’s break down each option and determine the correct values required for the installation. A) The secret key of WS1 - Explanation: The secret key is not required for configuring the Microsoft Enterprise Cloud Monitoring extension. The extension typically uses a workspace ID and workspace key to authenticate and send logs to a Log Analytics workspace, but these are not considered "secret keys" in this context. - Conclusion: This is not the correct answer as secret keys are not part of the configuration for this extension. B) The ID of the subscription - Explanation: The ID of the subscription identifies the Azure subscription in which the Log Analytics workspace and virtual machine reside. While the subscription ID may be useful for resource management, it is not directly required to configure the extension. - Conclusion: While the subscription ID may be helpful in some scenarios, it is not a required value for configuring the extension. C) The system-assigned managed identity of VM1 - Explanation: System-assigned managed identity is used to give an Azure resource (like VM1) an identity to authenticate with Azure resources. However, when installing the Microsoft Enterprise Cloud Monitoring extension... Author: Ella · Last updated May 25, 2026 |
You have an app named App1 that uses Application Insights to monitor application performance. You need to analyze how often a page in App1 is ...To analyze how often a page in your app (`App1`) is accessed in Application Insights, you need to look at metrics related to page views or user interactions with the app. Let's break down each option: A) Events - Explanation: The Events pane in Application Insights typically refers to specific custom events or telemetry items (such as custom events or traces) that are tracked in your application. While you could track page views as custom events, this pane is not specifically designed to track how often pages are accessed by default. - Conclusion: This is not the ideal choice for tracking page access, as it’s more focused on custom telemetry events, rather than page views or visits. B) Sessions - Explanation: The Sessions pane focuses on user sessions, meaning the activities performed by users during a single visit to the app. While it provides insights into user interactions during a session, it doesn't focus specifically on how often individual pages are accessed. - Conclusion: This is useful for understanding user activity during a session, but it doesn't provide the specific insight into how often a page is accessed.... Author: Liam123 · Last updated May 25, 2026 |
HOTSPOT - You have a project in Azure DevOps that includes two users named User1 and User2. You plan to use Azure Monitor to manage logs. You need to ensure that the users can perform the actions shown in following the table. The solution must follow the principle of least privilege. Which role should...Author: Vikram · Last updated May 25, 2026 |
DRAG DROP - You have a project in Azure DevOps. You need to configure a dashboard that will provide information on the following metrics. * How long it takes to close a work item * The number of completed backlog items * How long it takes to restore failed services Which type of widget should you use for each metric? To answer, drag the appropriate widget types to the correct metrics. Each widget ty...Author: Kunal · Last updated May 25, 2026 |
You have an Azure App Service app named App1. You need to identify when App1 was offline. The solution must minimize administrative effort. Which t...To identify when App1 was offline, the best troubleshooting category in App Service diagnostics is D) Availability and Performance. Reasoning: 1. A) Navigator: - Scenario: This option helps you to discover features, resources, and their relationships within your app and its environment. It provides a navigation perspective rather than focusing on issues related to availability or performance. - Why Rejected: This category is more useful for exploring the application structure and relationships, not for pinpointing downtime or availability issues. 2. B) Configuration and Management: - Scenario: This category deals with configuration settings and management aspects like app settings, scaling configurations, and deployments. - Why Rejected: This is useful for managing the app's configuration but doesn't directly address the availability or downtime monitoring. It's more about how the app is set up, not when it went offline. 3. C) Diagnostic Tools: - Scenario: Diagnostic Tools pr... Author: Vikram · Last updated May 25, 2026 |
You have an Azure subscription that contains an Azure Kubernetes Service (AKS) instance named AKS1. You collect and analyze metrics for AKS1 by using the Azure Monitor managed service for Prometheus. ...To analyze the performance of an Azure Kubernetes Service (AKS) instance using the Azure Monitor managed service for Prometheus, the correct query language is B) PromQL. Reasoning: 1. A) PL/SQL: - Scenario: PL/SQL (Procedural Language/SQL) is a procedural extension of SQL primarily used with Oracle databases. - Why Rejected: PL/SQL is designed for querying and managing relational databases like Oracle, not for monitoring Kubernetes performance or interacting with metrics in Prometheus. It is not suitable for analyzing AKS performance via Azure Monitor managed service for Prometheus. 2. B) PromQL: - Scenario: PromQL (Prometheus Query Language) is the query language used for querying metrics collected by Prometheus, including those stored and analyzed via the Azure Monitor managed service for Prometheus. - Why Selected: Since you are using Azure Monitor with Prometheus for AKS, PromQL is specifically designed to query time-series data and metrics lik... Author: MysticJaguar44 · Last updated May 25, 2026 |
HOTSPOT - You are interrogating logs by using KQL. You execute the query shown in the following exhibit. Use the drop-down menus to select the answer choice that completes each statement based on th...Author: Carlos Garcia · Last updated May 25, 2026 |
SIMULATION - For the RG1lod12345678 resource group, you need to create an action group named DevOpsAG that can be triggered in any region by using Alerts. The action group must email two users named [email protected] and [email protected] and notify me...Author: Lucas Carter · Last updated May 25, 2026 |
SIMULATION - You need to write a KQL query that will count the number of inbound requests for each source IP address, for any connection made during the last three months of 2021. On Azure Data Explorer by using the following link: https://dataexplorer.azure.corn/clusters/help/databases/SecurityLogs The requests are contained in a table named Inboun...Author: Maya · Last updated May 25, 2026 |
HOTSPOT - You have an Azure subscription that contains multiple web apps. You need to enable Change Analysis for the web apps. How should you complete the script? To answer, select the appro...Author: Kai · Last updated May 25, 2026 |
You have an Azure subscription that contains multiple Azure services. You need to send an SMS alert when scheduled maintenance is planned for the Azure services. Which two actions should you perform? Each corr...To send an SMS alert when scheduled maintenance is planned for Azure services, the appropriate steps involve setting up alerts and notifications specifically related to maintenance events. Let's analyze the available options: Option Analysis: A) Enable Azure Security Center: - Reason for Rejection: Azure Security Center primarily focuses on security-related alerts, compliance, and threat detection, and is not directly concerned with sending SMS alerts for scheduled maintenance. While Azure Security Center can notify you about security risks or vulnerabilities, it is not designed for handling planned maintenance events. - Scenario: Azure Security Center is used for monitoring security, not for scheduled maintenance notifications, so this option is not suitable. B) Create and configure an Azure Monitor alert rule: - Reason for Rejection: Azure Monitor alert rules are useful for monitoring resource performance and operational health (e.g., CPU usage, service outages), but they are not specifically designed to alert for scheduled maintenance. These alerts focus on detecting issues with the services themselves (e.g., health or performance metrics), rather than planned events like maintenance. - Scenario: While Azure Monitor alerts are powerful for operational monitoring, they are not intended to notify about scheduled maintenance events. Therefore, this option is not the best fit for the scenario. C) Create an Azure Service Health... Author: Liam · Last updated May 25, 2026 |
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure DevOps organization named Contoso and an Azure subscription. The subscription contains an Azure virtual machine scale set named VMSS1 that is configured for autoscaling. You have a project in ...Analysis: The goal is to ensure that an email alert is generated whenever the Azure Virtual Machine Scale Set (VMSS1) scales in or out. Let’s break down the solution step-by-step and analyze the provided option: Solution: "From Azure Monitor, configure the autoscale settings." - Azure Monitor Autoscale Settings: - Azure Monitor allows you to configure autoscale settings to automatically scale resources like VMSS1 based on metrics (e.g., CPU usage, memory usage). - However, autoscale settings themselves do not trigger notifications directly. Autoscaling just sets the conditions for scaling in or out. - For email alerts to be sent when scaling events occur (scaling in or out), you need to configure an alert rule that monitors the scaling events. Azure Monitor Alert rules would capture these events, but the autoscale configuration alone will not trigger... Author: CrystalWolfX · Last updated May 25, 2026 |
You configure Azure Application Insights and the shared service plan tier for a web app. You enable Smart Detection. You confirm that standard metrics are visible in the logs, but when you test a failure, you do not receive...Analysis: You are configuring Azure Application Insights with Smart Detection for a web app, but you're not receiving a Smart Detection notification when testing a failure. Let's go through each option to identify why the Smart Detection notification is not being sent. Option A) "You must enable the Snapshot Debugger for the web app." - Reason for Rejection: The Snapshot Debugger is a tool for capturing and diagnosing exceptions in real-time, but it is not required for Smart Detection. Smart Detection analyzes patterns in your app's performance and health and triggers alerts when it detects anomalies. The Snapshot Debugger is unrelated to the behavior of Smart Detection itself. - Scenario: This option is not relevant because enabling the Snapshot Debugger does not impact the Smart Detection notification process. Option B) "Smart Detection uses the first 24 hours to establish the normal behavior of the web app." - Reason for Selection: Smart Detection requires time to establish a baseline of normal application behavior, which typically takes 24 hours. During this period, Smart Detection learns what constitutes "normal" performance metrics for the web app. If you test a failure before this learning period is complete, Smart Detection may not yet be able to detect the anomaly, and thus no notification will be sent. - Scenario: This option explains why the Smart Detection notification is not being sent after testing a failur... Author: Aditya · Last updated May 25, 2026 |
DRAG DROP - You are planning projects for three customers. Each customer's preferred process for work items is shown in the following table. The customers all plan to use Azure DevOps for work item management. Which work item process should you use for each customer? To answer, drag the appropriate work item processes to the correct customers. Each work item process may be used once, more...Author: Sofia2021 · Last updated May 25, 2026 |
You configure an Azure Application Insights availability test. You need to notify the customer services department at your company by email when availability is degraded. You create an Azure logic app that will handle ...Analysis: To notify the customer services department by email when the availability test in Azure Application Insights is degraded, you are using an Azure Logic App. The goal is to invoke this Logic App when the availability status changes (degrades). Let's evaluate the available trigger types. Option A) HTTPWebhook trigger: - Reason for Selection: The HTTPWebhook trigger is commonly used for scenarios where you want to trigger an action (such as a Logic App) from an external service using an HTTP request. In this case, Azure Application Insights availability tests can be configured to send HTTP webhook notifications when a test fails or when availability degrades. - Scenario: Application Insights can be set up to call an HTTP endpoint (in this case, the Logic App’s HTTP Webhook trigger) when an availability test fails or is degraded. This trigger is designed for receiving an HTTP request from an external system like Application Insights, making it the right choice for invoking the Logic App based on availability degradation. Option B) HTTP trigger: - Reason for Rejection: The HTTP trigger in Azure Logic Apps is also used to initiate a workflow from an HTTP request. However, the HTTPWebhook trigger is more specialized for handling webhook notifications, which are commonly used for alerts and notifications like those from Application Insights. - Scenario: While the HTTP trigger could technically work, HTTPWebhook trigger is the recommended and more fitting trigger for receiving HTTP requests from external services like Application Insights. HTTPWebhook is more specific for these webhook-based use cases. Option C... Author: Benjamin · Last updated May 25, 2026 |
You have an Azure DevOps organization named Contoso and an Azure subscription. You use Azure DevOps to build a containerized app named App1 and deploy App1 to an Azure container instance nam...Analysis: In this scenario, the objective is to restart an Azure Container Instance (ACI1) when the application App1 stops responding. This requires setting up a mechanism that can monitor the health of App1 within ACI1 and automatically take action (e.g., restart the container) when it becomes unresponsive. Let’s evaluate the available options: Option A) Add a liveness probe to the YAML configuration of App1. - Reason for Selection: The liveness probe is used to check whether an application inside a container is still running and responsive. If the liveness probe detects that the application is not responding (i.e., the probe fails), Kubernetes or the container orchestrator can automatically restart the container to recover from the failure. While Azure Container Instances (ACI) doesn’t fully support all Kubernetes features, it does support liveness probes through the container's YAML configuration. - Scenario: The liveness probe is specifically designed to monitor an application's health and trigger a container restart if the app becomes unresponsive, making it the best solution for ensuring App1 is restarted if it stops responding. This will meet the goal of restarting ACI1 when App1 stops responding. Option B) Add a readiness probe to the YAML configuration of App1. - Reason for Rejection: The readiness probe checks if the application is ready to serve traffic. It is primarily used to determine if a container is ready to start receiving requests (e.g., HTTP traffic) but does not handle container restarts when the application is unresponsive. A readiness probe will not restart the container if the application stops responding; it merely prevents traffic from being sent to the container while it's in a non-ready state. - Scenario: A readine... Author: Noah Williams · Last updated May 25, 2026 |
You have a multi-tier application that has an Azure Web Apps front end and an Azure SQL Database back end. You need to recommend a solution to capture and store telemetry data. The solution must meet the following requirements: * Support using ad-hoc queries to identify baselines. * Trigger alerts when metrics in th...Analysis: The goal is to capture and store telemetry data for a multi-tier application (with an Azure Web Apps front end and an Azure SQL Database back end), while meeting the following requirements: 1. Support ad-hoc queries to identify baselines. 2. Trigger alerts when metrics in the baseline are exceeded. 3. Store application and database metrics in a central location. Let's go through the available options: Option A) Azure Event Hubs - Reason for Rejection: Azure Event Hubs is a highly scalable data streaming platform used for collecting and processing large amounts of event data in real time. While it can handle the ingestion of telemetry data, it does not provide built-in capabilities to store telemetry data, support ad-hoc queries, or trigger alerts. Event Hubs is typically used as a source for streaming data and requires additional processing tools (like Azure Stream Analytics or custom applications) to store, analyze, and trigger alerts. - Scenario: While it could be part of a larger solution (e.g., used to stream telemetry data into other services), Event Hubs does not meet the requirement for central telemetry storage or built-in querying and alerting capabilities. Option B) Azure SQL Database Intelligent Insights - Reason for Rejection: Azure SQL Database Intelligent Insights focuses on providing insights into the performance and health of Azure SQL Database. It can monitor things like query performance, resource consumption, and other database-specific metrics, but it is not a complete solution for capturing both application and database telemetry data, nor does it support broad ad-hoc queries for general application metrics. It also lacks the comprehensive alerting and querying capabilities needed for the entire application. - Scenario: This option focuses only on Azure SQL Database performance insights, which does not fully satisfy the requirement for a central solution to store and query both application and database metrics. It's more narrowly focused and does not capture application telemetry for the web app. Option C) Azure Application Insights ... Author: Emma · Last updated May 25, 2026 |
You have an Azure DevOps organization named Contoso and an Azure subscription. The subscription contains an Azure virtual machine scale set named VMSS1 that is configured for autoscaling. You use Azure DevOps to build a web app named App1 and deploy App1 to VMSS1. App1 is used heavily and has usage patterns that vary on a weekly basis. You need to recommend a solution to...Analysis: In this scenario, we need to detect an abnormal rise in the rate of failed requests to App1, which is deployed on an Azure virtual machine scale set (VMSS1) and has varying usage patterns. The solution should minimize administrative effort, so it should be automated and easy to configure. Let's evaluate the available options: Option A) The Smart Detection feature in Azure Application Insights - Reason for Selection: Smart Detection in Azure Application Insights automatically detects anomalies in application performance, including metrics like failed requests, response times, and availability. It uses machine learning to analyze your app’s behavior and can automatically trigger an alert when it detects an abnormal rise in failed requests or other issues, making it a low-administration solution. This option is highly suited to detect abnormal patterns in metrics without requiring manual configuration of thresholds or baselines. - Scenario: Since App1 has varying usage patterns, Smart Detection will adapt to these changes over time, identifying unusual spikes in failed requests without the need for manual configuration. This solution minimizes administrative overhead and directly addresses the goal of detecting abnormal rises in failed requests. Option B) The Failures feature in Azure Application Insights - Reason for Rejection: The Failures feature in Azure Application Insights provides insights into the types of failures (e.g., 500 errors) that have occurred within the application. However, while it gives detailed information about failures, it does not automatically detect abnormal rises in failure rates or trigger alerts based on that data. You would need to manually configure an alert or query to detect abnormal increases in failed requests, which adds administrative overhead. - Scenario: This option provides important failure data but would require additional manu... Author: Ryan · Last updated May 25, 2026 |
SIMULATION - You need to ensure that Microsoft Visual Studio 2017 can remotely attach to an Azure Function named fa-11566895. To c...Author: Ella · Last updated May 25, 2026 |
You have an Azure subscription that contains resources in several resource groups. You need to design a monitoring strategy that will provide a consolidated view. The solution must support the following requirements: * Support role-based access control (RBAC) by using Azure Active Directory (Azure AD) identifies. * Include visuals from Azure Monitor that are generated by using the Kusto...To design a consolidated monitoring strategy that meets the specified requirements, you need to consider several key factors like role-based access control (RBAC), Kusto Query Language (KQL) integration, the ability to use visuals, support for markdown documentation, and access to the latest data. Let's evaluate each option: Option A: Azure Monitor Azure Monitor is a comprehensive monitoring solution for collecting, analyzing, and acting on telemetry from your cloud and on-premises environments. It supports role-based access control (RBAC), integration with KQL (used for querying log data in Azure), and includes visualizations for monitoring. However, it does not have native markdown support for documentation or a consolidated view that spans multiple resource groups in a way that matches all the requirements for a consolidated reporting/dashboard. Why it's rejected: Although Azure Monitor can meet most of the requirements for data analysis and role-based access control, it does not provide a streamlined method for markdown documentation integration or for creating highly customized consolidated views across multiple resource groups with markdown support. Option B: Microsoft Power BI Microsoft Power BI is a powerful business analytics service that can integrate with Azure Monitor to create custom dashboards and visualizations. Power BI can consume Azure Monitor data using KQL and create visuals. It supports markdown for documentation and can generate rich visual reports that can be shared with role-based access control through Azure AD. Why it's rejected: While Power BI excels at visualization and integrates well with Azure data sources, it is not designed specifically for real-time monitoring with the latest data from Azure Monitor. Additionally, Power BI may require additional configuration to maintain up-to-date data in real-time, and setting up K... Author: Henry · Last updated May 25, 2026 |
You are automating the testing process for your company. You need to automate UI testing of a web a...To automate UI testing of a web application, you need to select a framework that is specifically designed for web application automation, allowing interaction with the user interface, element identification, and validation of UI components. Let's evaluate the given options: Option A: JaCoCo JaCoCo is a code coverage library primarily used for Java applications. It helps to measure the code coverage of unit tests (i.e., it shows which parts of the code are being exercised by tests). However, JaCoCo is not designed for UI testing, and it does not provide any facilities to interact with a web application's interface or automate UI actions. Why it's rejected: JaCoCo is for measuring code coverage in unit tests, not for automating UI tests in web applications. Option B: Selenium Selenium is one of the most popular open-source frameworks for automating web applications' UI tests. It supports multiple programming languages (e.g., Java, Python, C, etc.) and allows interaction with web elements like buttons, input fields, and links. It also provides the ability to simulate user actions such as clicks, text entry, and navigation. Selenium is highly customizable and can be integrated with various other testing tools and frameworks for continuous integration/continuous deployment (CI/CD) pipelines. Why it's selected: Selenium is specifically designed for web UI testing and is widely used in the industry. It supports a wide range of browsers and platforms, and it's compatible with many testing tools. I... Author: Ming · Last updated May 25, 2026 |
You are building an ASP.NET Core application. You plan to create an application utilization baseline by capturing telemetry data. You need to add code to the application to capture the telemetry data. The solution must minimize the costs of storing the telemetry data. Which two acti...To capture telemetry data in an ASP.NET Core application while minimizing the costs of storing the telemetry data, we need to focus on the best practices for telemetry collection that balance data capture and cost-efficiency. Let's evaluate each option: Option A: Add the `<InitialSamplingPercentage>99</InitialSamplingPercentage>` parameter to the ApplicationInsights.config file This parameter sets the initial sampling percentage for telemetry data. It allows controlling the percentage of telemetry data that is collected, which helps reduce the volume of data sent to Azure Application Insights. While this can help in reducing data volume, it doesn't provide dynamic adjustment or intelligent sampling based on application usage, making it a less efficient option. Why it's rejected: While this option reduces data volume by sampling, it is static and doesn't allow for adaptive adjustments based on load or conditions. It’s not as flexible as adaptive sampling, which can optimize data collection dynamically. Option B: From the code of the application, enable adaptive sampling Enabling adaptive sampling in your application code ensures that telemetry data is collected dynamically based on traffic patterns. When traffic is high, adaptive sampling reduces the amount of data collected by sampling only a fraction of the requests. During low traffic, it ensures more data is captured. This approach balances cost and data collection dynamically. Why it's selected: This option is the best approach for minimizing costs while ensuring meaningful telemetry data. Adaptive sampling automatically adjusts to traffic fluctuations, making it much more efficient than static sampling configurations. It provides both low-cost and high-quality telemetry. Option C: From the code of the application, add Azure Application Insights telemetry This step is necessary to enable telemetry collection in your application. It involves adding the Appli... Author: David · Last updated May 25, 2026 |
You have an Azure DevOps organization named Contoso and an Azure subscription. The subscription contains an Azure virtual machine scale set named VMSS1 and an Azure Standard Load Balancer named LB1. LB1 distributes incoming requests across VMSS1 instances. You use Azure DevOps to build a web app named App1 and deploy App1 to VMSS1. App1 is accessible via HTTPS only and configured to require mutual authentication by using a client certificate. You need to recommend a solution for implementing a health check of App1. T...To implement a health check for App1 hosted on an Azure Virtual Machine Scale Set (VMSS1) that minimizes administrative effort and meets the stated requirements, let's evaluate each option: Option A: An Azure Load Balancer health probe An Azure Load Balancer health probe is used to check the health of the virtual machines in a scale set. It works by sending regular probes (typically TCP or HTTP) to an endpoint on the VMs to ensure that they are healthy and available. The health probe is configured to check if the VM is responsive and can handle traffic. This option could meet the requirement of identifying whether individual VMSS1 instances are healthy and eligible for an upgrade. Why it’s rejected: Although the Load Balancer health probe can identify whether a VM is healthy, it doesn’t handle the mutual authentication via a client certificate, as required by App1, since the load balancer probes are often based on simple HTTP or TCP requests. Furthermore, it doesn’t give insight into the specific readiness for an upgrade operation, as it simply checks whether the VM is responding. Option B: Azure Monitor autoscale Azure Monitor autoscale is a feature that allows scaling based on metrics or conditions, such as CPU utilization or request count. While autoscale can be used to scale a VMSS automatically based on health metrics, it is not directly used for health checks of an individual instance. It is more focused on scaling rather than determining whether a specific VM instance is ready for an upgrade or identifying its health state. Why it’s rejected: Azure Monitor autoscale is designed for scaling resources, not for performing health checks on individual instances in terms of readiness for upgrades. This does not fulfill the need to check the health of App1 with mutual authentication or the eligibility for an upgrade operation. Option C: The Custom Script Extension The Custom Script Extension can be used to run scripts on individual VM instances in the scale set. These scripts can perform custom health checks, such as checking application health, and can interac... Author: Akash · Last updated May 25, 2026 |
HOTSPOT - You have an application named App1 that has a custom domain of app.contoso.com. You create a test in Azure Application Insights as shown in the following exhibit. Use the drop-down menus to select the answer choice that completes each statement...Author: StarryEagle42 · Last updated May 25, 2026 |
You have a build pipeline in Azure Pipelines that occasionally fails. You discover that a test measuring the response time of an API endpoint causes the failures. You need to prevent the build pipeline from failing due to the test. Which two actions should y...To address the issue of a failing test related to the response time of an API endpoint in Azure Pipelines, the solution must prevent the pipeline from failing due to intermittent issues caused by that specific test, such as slow response times. Let’s evaluate the options: Option A: Set Flaky test detection to Off Flaky test detection is a feature in Azure Pipelines that helps identify tests that intermittently fail (flaky tests). Turning this feature off would prevent the pipeline from considering a test flaky and prevent it from affecting the overall test result, potentially preventing pipeline failures due to those tests. Why it’s rejected: While this prevents flaky tests from affecting the pipeline, it does not resolve the root cause of the test failure. It also removes the ability to track and fix flaky tests in the future, which could lead to ignoring potential underlying issues. This approach is not the most effective as it stops detection, but it doesn't prevent failures if the test is genuinely failing or performing poorly. Option B: Clear Flaky tests included in test pass percentage This option would prevent flaky tests from affecting the pass percentage of the tests in the pipeline. By clearing flaky tests from the pass percentage calculation, it prevents them from artificially lowering the pass rate. Why it’s selected: This is an appropriate solution because it addresses the impact of flaky tests on the overall test results. If a flaky test is causing occasional failures due to timing issues (like response time), excluding it from the test pass percentage prevents it from causing the entire build to fail. It allows the pipeline to focus on tests that consistently pass or fail. Option C: Enable Test Impact Analysis (TIA) Test Impact Analysis (TIA) is a feature that determines which tests are relevant based on changes in the codebase and only runs those tests. It helps optimize test execution, but it doesn't directly ... Author: Nathan · Last updated May 25, 2026 |
Your company hosts a web application in Azure. The company uses Azure Pipelines for the build and release management of the application. Stakeholders report that the past few releases have negatively affected system performance. You configure alerts in Azure Monitor. You need to ensure that new releases are only deployed to production if the releases meet defined perfo...To ensure that new releases are only deployed to production if they meet the defined performance baseline criteria in the staging environment, the solution must integrate into your Azure Pipelines release pipeline and allow for automated checks based on the performance metrics collected from the staging environment. Let's evaluate the options: Option A: An Azure Scheduler job Azure Scheduler is a service used for scheduling tasks like calling web services or running scripts at specified times. However, it is not inherently integrated with Azure Pipelines or the release process. It would not be able to automatically enforce performance checks within the context of a pipeline. Why it’s rejected: Azure Scheduler is more suited for scheduled tasks or time-based triggers rather than directly enforcing performance checks within a pipeline. It would require manual integration, and it doesn’t offer the specific gating mechanism needed to prevent deployments based on performance criteria. Option B: A trigger A trigger in Azure Pipelines is used to automatically start a pipeline or deployment process when certain conditions are met (e.g., a code commit). While triggers can initiate actions, they do not directly evaluate whether performance baselines have been met before proceeding with a deployment. It is more of a mechanism to start a pipeline rather than enforce checks before proceeding. Why it’s rejected: Triggers initiate processes but don't evaluate performance or impose conditions based on specific criteria. Therefore, a trigger alone cannot prevent a release from progressing if performance baselines are not met. Option C: A gate A gate in Azure Pipelines is a mechanism used to enforce conditions or checks before a deployment proceeds. Azure Pipelines gates can be ... Author: Ethan · Last updated May 25, 2026 |
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You manage a projec...Analysis of the Solution: The proposed solution is to perform a Subscription Health scan when packages are created. The goal is to prevent the configuration of the project from changing over time. Let's assess if this solution can achieve that goal. What a Subscription Health Scan Does: A Subscription Health scan in Azure typically helps assess the overall health of an Azure subscription, including detecting issues like misconfigurations, security vulnerabilities, and compliance risks. It helps ensure that your environment is compliant with best practices and governance policies but is focused on the infrastructure and subscription rather than the configuration management of the project itself in Azure DevOps. Why This Doesn't Meet the Goal: The task described in the question is to prevent configuration changes over time. A Subscription Health scan focuses on identifying issues with resources and services but does not control or prevent configuratio... Author: Sara · Last updated May 25, 2026 |
Your company uses the following resources: * Windows Server 2019 container images hosted in an Azure Container Registry. * Azure virtual machines that run the latest version of Ubuntu * An Azure Log Analytics workspace * Azure Active Directory (Azure AD) * An Azure key vault For which two resources can you receive vulner...Azure Security Center provides vulnerability assessments and security recommendations for various Azure resources. To address the question, let’s evaluate each resource and determine if it can receive vulnerability assessments: Option A: The Azure Log Analytics workspace Azure Log Analytics is used for collecting, analyzing, and visualizing logs and metrics from various sources. While Azure Security Center can integrate with Log Analytics for monitoring, vulnerability assessments are not performed directly on Log Analytics workspaces. The workspace is a tool for data collection, not a resource that can have its own vulnerabilities assessed. Why it’s rejected: Azure Log Analytics workspace itself does not undergo vulnerability assessments. It is used for analyzing the data from other resources but is not subject to vulnerability scanning. Option B: The Azure key vault Azure Key Vault is a service used to store and manage sensitive data such as secrets, certificates, and keys. While security considerations around Azure Key Vault are critical, Azure Security Center does not directly perform vulnerability assessments on the Key Vault. Instead, it focuses on the security posture and monitoring of the resources that interact with the Key Vault (such as ensuring proper access control policies). Why it’s rejected: Azure Security Center doesn’t directly conduct vulnerability assessments on Azure Key Vault. Instead, it monitors and provides security recommendations based on how it’s used and accessed. Option C: The Azure virtual machines that run the latest version of Ubuntu Azure Security Center can perform vulnerability assessments on Azure virtual machines, including those running Ubuntu or any other supported operating system. It checks for common security issues, misconfigurations, and vulnerabilities, ensuring that virtual machines are secure. For example, Security Center integrates with Qualys to run vulnerability scans on these VMs. Why it’s select... Author: Liam · Last updated May 25, 2026 |
You use Azure Pipelines to manage build pipelines, GitHub to store source code, and Dependabot to manage dependencies. You have an app named App1. Dependabot detects a dependency i...To apply a dependency update with Dependabot, the first step is to allow Dependabot to propose the update in the form of a pull request (PR). This PR will contain the necessary changes to update the dependency in your GitHub repository. Here’s why we select A) Create a pull request and reject the others: Key Factors: 1. Dependabot’s Role: Dependabot automatically detects outdated dependencies and generates a pull request with the required changes to your repository. The pull request includes the updated dependency and a description of the update. 2. Standard Workflow: After Dependabot creates the pull request, the next step is to review the proposed changes, not to manually create a branch or commit first. The PR itself is a signal that the dependency has been successfully detected and proposed for update. 3. Review & Testing: The PR allows for testing and review before merging. Onc... Author: Daniel · Last updated May 25, 2026 |
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You manage...Analysis of the proposed solution: In this scenario, the goal is to prevent the configuration of the project from changing over time. The proposed solution is to add a code coverage step to the build pipelines. Key Factors: 1. Code Coverage: Code coverage steps in a build pipeline are primarily focused on measuring and reporting how much of the source code is covered by automated tests. This step checks the effectiveness of the tests and identifies untested parts of the application. 2. Project Configuration Stability: Preventing the configuration of the project from changing over time is more about controlling access, enforcing policies, and managing configuration as code (e.g., using version-controlled infrastructure or access restrictions) to prevent unwanted changes to the project setup. 3. What Code Coverage Does Not Do: A code coverage step does not address the goal of preventing changes to project configuration, such as controlling settings, permissions, or other infrastructure configurations. It is focused on the qu... Author: Leah Davis · Last updated May 25, 2026 |
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You manage ...Analysis of the proposed solution: The goal is to prevent the configuration of the project from changing over time. The proposed solution is to implement Continuous Integration (CI) for the project. Key Factors: 1. Continuous Integration (CI): CI is a software development practice where code changes are automatically built, tested, and integrated into a shared codebase multiple times a day. It primarily focuses on automating the process of testing, building, and integrating code, helping to detect issues early in the development cycle. 2. Project Configuration Stability: Preventing changes to project configuration is more about controlling and managing configurations, access permissions, and policies, rather than automating integration and build processes. While CI helps in ensuring that the latest code is always integrated, it does not prevent changes to project configuration settings or infrastructure. 3. What CI Does Not Do: CI ensures code is integrated and tested frequently, but it doesn't directly address the goal of preventing the project configuration from changing. It will not enforc... Author: Ravi Patel · Last updated May 25, 2026 |
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You manag...Analysis of the proposed solution: The goal is to prevent the configuration of the project from changing over time. The proposed solution is to implement Continuous Assurance for the project. Key Factors: 1. Continuous Assurance: Continuous Assurance is a concept that integrates continuous monitoring and validation of policies, controls, and practices within a development lifecycle. It ensures that best practices and standards are consistently followed and can automatically detect deviations or non-compliance. 2. Project Configuration Stability: Preventing changes to project configuration involves enforcing policies and controls on the configuration and access settings. Continuous Assurance can play a role in ensuring that the configuration remains in compliance with predefined standards, monitoring for changes or deviations, and preventing unwanted changes to critical configurations over time. 3. How Continuous Assurance Helps: Continuous Assurance aims to enforce compliance and monitoring at every step, meaning it can help identify unauthorized or unapproved conf... Author: ElectricLionX · Last updated May 25, 2026 |
You are designing a configuration management solution to support five apps hosted on Azure App Service. Each app is available in the following three environments: development, test, and production. You need to recommend a configuration management solution that meets the following requirements: * Supports feature flags * Tracks configuration changes from the past 30 days * Stores hierarchically structured configuration values * Controls access to the configurations by us...Analysis of the proposed solution: You need to recommend an Azure service for configuration management that supports the following requirements: 1. Supports feature flags. 2. Tracks configuration changes from the past 30 days. 3. Stores hierarchically structured configuration values. 4. Controls access to the configurations using RBAC permissions. 5. Stores shared values as key/value pairs that can be used by all apps. Key Considerations: - The service should support feature flags for toggling functionality between different environments (e.g., development, test, production). - The service should have version history to track changes over the past 30 days. - Hierarchical storage means configuration values should be organized in a tree-like structure (e.g., app settings for different environments). - RBAC access control is necessary for secure access management. - Shared values should be able to be accessed by multiple apps, potentially across environments. Review of Options: 1. A) Azure Cosmos DB: - Why it’s not suitable: Azure Cosmos DB is a NoSQL database and is excellent for storing large-scale, globally distributed data. However, it doesn’t have built-in support for feature flags, version tracking, or hierarchical structure tailored to configuration management. While Cosmos DB can store key/value pairs, it lacks the specialized functionality for managing configuration settings, tracking changes, and controlling access in a structured way. 2. B) Azure App Service: - Why it’s not suitable: Azure App Service is a platform for hosting web apps and APIs. While it can manage app settings (like environment variables), it is not a configuration management service. It doesn’t natively support feature flags, version tracking, or advanced RBAC for configuration management. It also doesn’t provide a hierarchical structure for storing... Author: Suresh · Last updated May 25, 2026 |
You have a containerized solution that runs in Azure Container Instances. The solution contains a frontend container named App1 and a backend container named DB1. DB1 loads a large amount of data during startup. You need to verify that ...To solve this problem, you need to ensure that the backend container, DB1, is fully ready and can handle incoming requests before the frontend container, App1, starts accepting user requests. Let's evaluate the options: A) Liveness Probe - What it is: A liveness probe checks if a container is still running and functioning. It helps Kubernetes or container orchestrators detect when a container is unhealthy and needs to be restarted. - Why it's not suitable: While a liveness probe ensures the container is alive, it doesn't ensure that DB1 is fully ready to process requests, particularly if it needs to load data during startup. It's more for determining if the service inside the container is responsive, not whether it's ready to handle traffic after initialization. B) Performance Log - What it is: Performance logs are used to track performance metrics, such as CPU and memory usage, but they don’t actively ensure that DB1 is ready to handle requests. - Why it's not suitable: Logs are useful for tracking system performance but don't provide a mechanism to prevent requests from being sent to App1 before DB1 is ready. They don't address the readiness check for incoming requests. C) Readiness Probe - What it is: A readiness probe checks if a container is ready to accept... Author: Akash · Last updated May 25, 2026 |
You are designing a strategy to monitor the baseline metrics of Azure virtual machines that run Windows Server. You need to collect detailed data about the processes running in the guest operating system. Which two agents should you deplo...To collect detailed data about processes running in the guest operating system on Azure Virtual Machines (VMs) running Windows Server, it's essential to choose the right agents for monitoring. Let's evaluate the options: A) Telegraf agent - What it is: Telegraf is an open-source agent for collecting metrics and data, often used in conjunction with tools like InfluxDB. It can collect data from various sources, including system metrics, application data, and network statistics. - Why it's not suitable: While Telegraf can collect detailed performance data, it's not the native solution within Azure for monitoring Windows Server VMs. In Azure, we typically rely on Microsoft-provided agents like the Azure Log Analytics agent for better integration with Azure Monitor and other monitoring tools. B) Azure Log Analytics agent - What it is: The Azure Log Analytics agent (formerly known as the OMS agent) collects telemetry data from the operating system, including detailed data on processes, performance, and health. This agent integrates directly with Azure Monitor and Log Analytics workspaces to collect and store performance and event data. - Why it's suitable: This is the most common and preferred agent for monitoring Windows Server VMs in Azure. It collects detailed system and application-level data, including running processes, performance metrics, and logs. It's the primary agent used to monitor virtual machines and provides comprehensive insights for baseline metric collection. C) Azure Network Watcher Agent for Windows -... Author: Kai · Last updated May 25, 2026 |
DRAG DROP - You use Azure Pipelines to automate Continuous Integration/Continuous Deployment (CI/CD) for an Azure web app named WebApp1. You configure an Azure Monitor alert that is triggered when WebApp1 generates an error. You need to configure the alert to forward details of the error to a third-party system. The solution must minimize administrative effort. Which three actions shou...Author: Leah Davis · Last updated May 25, 2026 |