SIMULATIONFor 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 admin1@contoso.com and admin2@contoso.com and notify members of the Owner role for the resource.Use only the common alert schema for notifying the resource owners.
Answer(s): A
See explanation below.Create an action group in the Azure portalStep 1: Go to the Azure portal.Step 2: Search for and select Monitor. The Monitor pane consolidates all your monitoring settings and data in one view.Step 3: Select Alerts, and then select Action groups.Step 4: Select Create.Step 5: Configure basic action group settings. In the Project details section:Select values for Subscription and Resource group [Select RG1lod12345678].Select the region.The action group is saved in the subscription, region, and resource group that you select.Step 6: In the Instance details section, enter values for Action group name [Enter DevOpsAG ] and Display name. The display name is used in place of a full action group name when the group is used to send notifications.Step 7: Configure notifications. Select Next: Notifications, or select the Notifications tab at the top of the page.Step 8: Define a list of notifications to send when an alert is triggered.Step 9: For each notification:9a. Select the Notification type, and then fill in the appropriate fields for that notification. The available options are:* Email Azure Resource Manager roleSend an email to the subscription members, based on their role. [Choose the Owner role]Enter the primary email address configured for the Microsoft Entra user.9b. Select if you want to enable the Common alert schema. [Skip]9c. Select OK.* EmailEnter the email where the notification should be sent. [Enter admin1@contoso.com and admin2@contoso.com]Step 10: Finished the Wizard.* Details omitted *
https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/action-groups
You have an Azure DevOps organization named Contoso.You need to receive Microsoft Teams notifications when work items are updated.What should you do?
Answer(s): B
DRAG DROP (Drag and Drop is not supported)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 servicesWhich type of widget should you use for each metric? To answer, drag the appropriate widget types to the correct metrics. Each widget type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.Note: Each correct selection is worth one point.Select and Place:
Box 1: Lead timeHow long it takes to close a work itemLead time measures the total time elapsed from the creation of work items to their completion.The Burndown widget lets you display a trend of remaining workThe Lead Time widget will help you analyze the time it takes to deliver work from your backlogBox 2: VelocityThe number of completed backlog itemsVelocity provides a useful metric for these activities:Support sprint planning*-> Forecast future sprints and the backlog items that can be completedA guide for determining how well the team estimates and meets their planned commitmentsBox 3: Cycle timeHow long it takes to restore failed servicesCycle time measures the time it takes for your team to complete work items once they begin actively working on them.The Cycle Time widget will help you analyze the time it takes for your team to complete work items once they begin actively working on themIncorrect:* BurndownBurndown and burnup charts support project management to visually track work completed over time. Burndown charts begin with the total amount of planned work and then as work is completed graphs the remaining work. With the progression of time, the amount of to-do work decreases.Burnup charts track work as it is completed over time. They're useful to show the rate at which work is getting completed.Mean time to recovery (MTTR) measures how long it takes to recover from a partial service interruption or total failure. This is an important metric to track.Incorrect:* VelocityWhat Is Velocity in Azure DevOps?Velocity, in the agile methodology, is defined as the rate of progress in software development from one sprint to the next. That is, it’s the amount of work your team manages to get done within the current sprint, before moving on to the next sprint.And what’s the point of measuring velocity?As you continue to keep track of your team’s velocity from previous sprints, it’ll help you establish a pattern that leads to better budget estimates and deadline forecasts. You’ll have a better understanding of the time and effort required to complete a new project, which will empower you to make better decisions as a team leadNote: The Lead Time and Cycle Time widgets indicate how long it takes for work to flow through your development pipeline. Lead time measures the total time elapsed from the creation of work items to their completion. Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.The following diagram illustrates how lead time differs from cycle time. Lead time is calculated from work item creation to entering a completed state. Cycle time is calculated from first entering an In Progress or Resolved state category to entering a Completed state category.
https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time https://learn.microsoft.com/en-us/azure/devops/report/dashboards/burndown-guidance
HOTSPOT (Drag and Drop is not supported)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 webapp1 after each modification.What should you do? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Modify ApplicationInsights.configIn ApplicationInsights.config, you can adjust several parameters in the AdaptiveSamplingTelemetryProcessor node. The figures shown are the default values:<MaxTelemetryItemsPerSecond>5</MaxTelemetryItemsPerSecond>The target rate of logical operations that the adaptive algorithm aims to collect on each server host. If your web app runs on many hosts, reduce this value so as to remain within your target rate of traffic at the Application Insights portal.<EvaluationInterval>00:00:15</EvaluationInterval>The interval at which the current rate of telemetry is reevaluated. Evaluation is performed as a moving average. You might want to shorten this interval if your telemetry is liable to sudden bursts.Etc.Box 2: Modify the Usage and estimated costs settings.Ingestion samplingUse this type of sampling if your app often goes over its monthly quota and you don't have the option of using either of the SDK-based types of sampling.Set the sampling rate in the Usage and estimated costs page:Incorrect:* Smart detectionProactive diagnostics is a recent feature. Without any special configuration by you, Application Insights automatically detects and alerts you about unusual rises in failure rates in your app. It's smart enough to ignore a background of occasional failures, and also rises that are simply proportionate to a rise in requests. So for example, if there's a failure in one of the services you depend on, or if the new build you just deployed isn't working so well, then you'll know about it as soon as you look at your email. (And there are webhooks so that you can trigger other apps.)Another aspect of this feature performs a daily in-depth analysis of your telemetry, looking for unusual patterns of performance that are hard to discover. For example, it can find slow performance associated with a particular geographical area, or with a particular browser version.* Continuous ExportWant to keep your telemetry for longer than the standard retention period? Or process it in some specialized way? Continuous Export is ideal for this purpose. The events you see in the Application Insights portal can be exported to storage in Microsoft Azure in JSON format. From there, you can download your data and write whatever code you need to process it.
https://docs.microsoft.com/en-us/azure/azure-monitor/app/sampling https://docs.microsoft.com/en-us/azure/azure-monitor/app/devops#smart-detection
HOTSPOT (Drag and Drop is not supported)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 appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Register-AzResourceProvider-ProviderNamespaceEnable Change Analysis at scale using PowerShellRun the following script.# Log in to your Azure subscriptionConnect-AzAccount# Get subscription Id$SubscriptionId = Read-Host -Prompt 'Input your subscription Id'# Make Feature Flag visible to the subscriptionSet-AzContext -SubscriptionId $SubscriptionId# Register resource providerRegister-AzResourceProvider -ProviderNamespace "Microsoft.ChangeAnalysis" [Box 1]# Enable each web app$webapp_list = Get-AzWebApp | Where-Object {$_.kind -eq 'app'}foreach ($webapp in $webapp_list){$tags = $webapp.Tags$tags["hidden-related:diagnostics/changeAnalysisScanEnabled"]=$trueSet-AzResource -ResourceId $webapp.Id -Tag $tags -Force [Box 2]}Box 2: Set-AzResource -ResourceId
https://learn.microsoft.com/en-us/azure/azure-monitor/change/change-analysis-enable
Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members: