Download Microsoft.AZ-400.Dump4Pass.2024-03-24.288q.tqb

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

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/

Service hooks let you run tasks on other services when events happen in your Azure DevOps projects. For example, create a card in Trello when a work item is created or send a push notification to your team's mobile devices when a build fails. You can also use service hooks in custom apps and services as a more efficient way to drive activities when events happen in your projects.    Note: Service hook publishers define a set of events. Subscriptions listen for the events and define actions to take based on the event. Subscriptions also target consumers, which are external services that can run their own actions, when an event occurs.    Reference: https://docs.microsoft.com/en-us/azure/devops/service-hooks/overview

Box 1: 5 minutes The alert must calculate the average once every minute.    Note: We [Microsoft] recommend choosing an Aggregation granularity (Period) that is larger than the Frequency of evaluation, to reduce the likelihood of missing the first evaluation of added time series    Box 2: Static   Box 3: Greater than   Example, say you have an App Service plan for your website. You want to monitor CPU usage on multiple instances running your web site/app. You can do that using a metric alert rule as follows: Target resource: myAppServicePlan Metric: Percentage CPU Condition Type: Static Dimensions  Instance = InstanceName1, InstanceName2  Time Aggregation: Average Period: Over the last 5 mins Frequency: 1 min Operator: GreaterThan Threshold: 70 Like before, this rule monitors if the average CPU usage for the last 5 minutes exceeds 70%.  Aggregation granularity    Reference:   https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-metric-overview

Box 1: every five minutes at a random location Test frequency: Sets how often the test is run from each test location. With a default frequency of five minutes and five test locations, your site is tested on average every minute.    Box 2: Parse dependent requests: Test requests images, scripts, style files, and other files that are part of the web page under test. The recorded response time includes the time taken to get these files. The test fails if any of these resources cannot be successfully downloaded within the timeout for the whole test.  Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/app/monitor-web-app-availability

Scenarios and use cases for gates include: Quality validation. Query metrics from tests on the build artifacts such as pass rate or code coverage and deploy only if they are within required thresholds.    Use Quality Gates to integrate monitoring into your pre-deployment or post-deployment. This ensures that you are meeting the key health/performance metrics (KPIs) as your applications move from dev to production and any differences in the infrastructure environment or scale is not negatively impacting your KPIs.    Note: Gates allow automatic collection of health signals from external services, and then promote the release when all the signals are successful at the same time or stop the deployment on timeout. Typically, gates are used in connection with incident management, problem management, change management, monitoring, and external approval systems.    Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/continuous-monitoring   https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops