Download Microsoft.AZ-400.Dump4Pass.2024-04-20.338q.vcex

Box 1: percentile_duration_95   Box 2: success For example –  requests  | project name, url, success  | where success == "False"  This will return all the failed requests in my App Insights within the specified time range.    Reference: https://devblogs.microsoft.com/premier-developer/alerts-based-on-analytics-query-using-custom-log-search/

B: Metric Alert with Dynamic Thresholds detection leverages advanced machine learning (ML) to learn metrics' historical behavior, identify patterns and anomalies that indicate possible service issues. It provides support of both a simple UI and operations at scale by allowing users to configure alert rules through the Azure Resource Manager API, in a fully automated manner.    A: You can use Azure Monitor to monitor base-level metrics and logs for most services in Azure. You can call Azure Automation runbooks by using action groups or by using classic alerts to automate tasks based on alerts.    Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-dynamic-thresholds   https://docs.microsoft.com/en-us/azure/automation/automation-create-alert-triggered-runbook

Box 1: readinessProbe: For containerized applications that serve traffic, you might want to verify that your container is ready to handle incoming requests. Azure Container Instances supports readiness probes to include configurations so that your container can't be accessed under certain conditions.    Incorrect Answers: livenessProbe: Containerized applications may run for extended periods of time, resulting in broken states that may need to be repaired by restarting the container. Azure Container Instances supports liveness probes so that you can configure your containers within your container group to restart if critical functionality is not working.  Box 2: periodSeconds: 15 The periodSeconds property designates the readiness command should execute every 15 seconds.    Reference: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-readiness-probe

Step 1: Create an instance of Azure Application Insights 1. Open Microsoft Azure Portal  2. Log into your Azure account, Select Create a resource > Developer tools > Application Insights.               3. Enter the following settings, and then select Review + create.  Name: az400-9940427-main   Step 2: Configure App Insights SDK 1. Open your ASP.NET Core Web App project in Visual Studio > Right-click on the AppName in the Solution Explorer > Select Add > Application Insights Telemetry.              2. Click the Get Started button  3. Select your account and subscription > Select the Existing resource you created in the Azure portal > Click Register.    Reference: https://docs.microsoft.com/bs-latn-ba/azure/azure-monitor/learn/dotnetcore-quick-start?view=vs-2017

Box 1: Basic Assign Basic to users with a TFS CAL, with a Visual Studio Professional subscription, and to users for whom you are paying for Azure Boards & Repos in an organization.    Box 2: Stakeholder Assign Stakeholders to users with no license or subscriptions who need access to a limited set of features.    Note: You assign users or groups of users to one of the following access levels:   Basic: provides access to most features VS Enterprise: provides access to premium features Stakeholders: provides partial access, can be assigned to unlimited users for free   Reference: https://docs.microsoft.com/en-us/azure/devops/organizations/security/access-levels?view=vsts

E: Exceptions in your live web app are reported by Application Insights.   Note: Periodical reports help keep a team informed on how their business critical services are doing. Developers, DevOps/SRE teams, and their managers can be productive with automated reports reliably delivering insights without requiring everyone to sign in the portal. Such reports can also help identify gradual increases in latencies, load or failure rates that may not trigger any alert rules.    A: You can programmatically query Application Insights data to generate custom reports on a schedule. The following options can help you get started quickly: Automate reports with Microsoft Flow  Automate reports with Logic Apps    Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/app/asp-net-exceptions   https://docs.microsoft.com/en-us/azure/azure-monitor/app/automate-custom-reports

The "Exploratory Testing" extension is now "Test & Feedback" and is now Generally Available.    Anyone can now test web apps and give feedback, all directly from the browser on any platform: Windows, Mac, or Linux. Available for Google Chrome and Mozilla Firefox (required version 50.0 or above) currently. Support for Microsoft Edge is in the pipeline and will be enabled once Edge moves to a Chromium-compatible web platform.    Reference: https://marketplace.visualstudio.com/items?itemName=ms.vss-exploratorytesting-web

1. Open Microsoft Azure Portal  2. Log into your Azure account and go to App Service and look under Monitoring then you will see Alert.  3. Select Add an alert rule  4. Configure the alert rule as per below and click Ok.  Source: Alert on Metrics Resource Group: az400-9940427-main Resource: az400-9940427-main Threshold: 5 Period: Over the last 5 minutes Webhook: https://contoso.com/notify              Reference: https://azure.microsoft.com/es-es/blog/webhooks-for-azure-alerts/

Box 1: requests Failed requests (requests/failed): The count of tracked server requests that were marked as failed.  Kusto code: requests  | where success == 'False'  Box 2: success == false Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/app-insights-metrics