DRAG DROP (Drag and Drop is not supported)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 processA burndown chart for the work in a single iterationHow long it takes to close a work item after the item was startedWhich 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:
Answer(s): A
Box 1: Burndown chartBottlenecks in the software development processInterpret a burndown or burnup chartYour team can get immediate insight as to their progress and learn about their rhythm and behavior. Most burndown lines aren't straight lines. The team never moves at exactly one fixed velocity. Scope increases occur over time. For example, if your projected completion date moves, you may want to ask one of these questions:Are we adding too much scope?Is the average burn rate changing, and if so, why?Burndown charts also help teams understand risks to their release. If the projected end date exceeds the release target date, teams may need to reduce scope or lengthen the project. Burndown can also indicate that progress is greater than expected, providing the uncommon, but wonderful option of adding scope.As the following diagram shows, charts based on the burndown/burnup widgets provide many calculated elements.Box 2: Cycle timeHow long it takes to close a work item after the item was startedCycle time measures the time it takes for your team to complete work items once they begin actively working on them.Box 3: Sprint burndownA burndown chart for the work in a single iterationThe definition of a sprint is a dedicated period of time in which a set amount of work will be completed on a project. It's part of the agile methodology, and an Agile project will be broken down into a number of sprints, each sprint taking the project closer to completion.The aim of a sprint is to make progress against the product goal. So the scrum team determines and agrees to a consistent duration for completing work. Most sprints range from two to four weeks -- but should not be longer than one month.Incorrect:* VelocityVelocity metrics provide useful information, so teams can plan and forecast sprints and determine how well they estimate and meet planned commitments. You can get an indication of how much work a team can complete during a sprint based on either a count of work items completed or the sum of estimates made for effort (product backlog items), story points (user stories), or size (requirements). Use velocity as an aid to determine team capacity and don't confuse it with key performance indicators.* Cumulative flow diagram (CFD)You use cumulative flow diagrams (CFD) to monitor the flow of work through a system. There are two CFD charts: the in-context report you can view from a team backlog or Kanban board and the CFD widget you can add to a dashboard.CFDs help teams monitor the count of work items as they progressively move through various workflow states. These diagrams can show the flow of epics, features, user stories, issues, product backlog items, or requirements, depending on the process selected for your project* Lead timeLead time measures the total time elapsed from the creation of work items to their completion.
https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time https://business.adobe.com/blog/basics/sprints .https://learn.microsoft.com/en-us/azure/devops/report/dashboards/configure-sprint-burndown
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 accessed.Which pane in Application Insights should you use?
HOTSPOT (Drag and Drop is not supported)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 you assign to each user? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Built-in monitoring rolesBuilt-in roles in Azure Monitor help limit access to resources in a subscription while still enabling staff who monitor infrastructure to obtain and configure the data they need. Azure Monitor provides two out-of-the-box roles: Monitoring Reader and Monitoring Contributor.Box 1: Monitoring ContributorPeople assigned the Monitoring Contributor role can view all monitoring data in a subscription. They can also create or modify monitoring settings, but they can't modify any other resources.This role is a superset of the Monitoring Reader role. It's appropriate for members of an organization's monitoring team or managed service providers who, in addition to the permissions mentioned earlier, need to:*-> View monitoring dashboards in the portal and create their own private monitoring dashboards.Create and edit diagnostic settings for a resource.Set alert rule activity and settings using Azure alerts.List shared keys for a Log Analytics workspace.Create, delete, and execute saved searches in a Log Analytics workspace. Create and delete the workspace storage configuration for Log Analytics. Create web tests and components for Application Insights. See Resources, roles, and access control in Application Insights.Box 2: Monitoring ReaderPeople assigned the Monitoring Reader role can view all monitoring data in a subscription but can't modify any resource or edit any settings related to monitoring resources. This role is appropriate for users in an organization, such as support or operations engineers, who need to:View monitoring dashboards in the Azure portal.View alert rules defined in Azure alerts.Query Azure Monitor Metrics by using the Azure Monitor REST API, PowerShell cmdlets, or cross-platform CLI.Query the Activity log by using the portal, Azure Monitor REST API, PowerShell cmdlets, or cross-platform CLI.View the diagnostic settings for a resource.View the log profile for a subscription.*-> View autoscale settings.*-> View alert activity and settings.Search Log Analytics workspace data, including usage data for the workspace.Retrieve the table schemas in a Log Analytics workspace.Retrieve and execute log queries in a Log Analytics workspace.Access Application Insights data.
https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
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 itemThe number of completed backlog itemsHow 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 work The 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 completed A 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
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.You need to analyze the performance of AKS1.Which query language should you use?
Answer(s): B
Azure Monitor managed service for PrometheusAzure Monitor managed service for Prometheus is a component of Azure Monitor Metrics, providing more flexibility in the types of metric data that you can collect and analyze with Azure Monitor. Prometheus metrics are supported by analysis tool like Azure Monitor Metrics Explorer with PromQL and open source tools such as PromQL and Grafana.
https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/prometheus-metrics-overview
HOTSPOT (Drag and Drop is not supported)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 the information presented in the graphic.Note: Each correct selection is worth one point.Hot Area:
Box 1: Six_____________ columns will be returned in the query output.Line 3 specifies five columns.Line 4 specifies an additional sixth column with extend.Box 2: timespanThe data type of the Duration column is _______________.One of the datatypes in Kusto is timespan. If you subtract two datetetime columns, the results is a timespan.Execute in [Web] [Desktop] [cluster('kuskuseus.eastus.kusto.windows.net').database('Kuskus')]print Span=datetime(2024-3-10 22:30)-datetime(2024-3-9 08:50)PrimaryResultSpan1.13:40:00Note: Kusto, extend operatorCreates calculated columns and append them to the result set.SyntaxT | extend [ColumnName | (ColumnName[, ...]) =] Expression [, ...]ExampleStormEvents| project EndTime, StartTime| extend Duration = EndTime - StartTimeThe following table shows only the first 10 results. To see the full output, run the query.
https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/extend-operator https://techcommunity.microsoft.com/t5/azure-data-explorer-blog/timespan-duration-values-in-kql-power-query- and-power-bi/ba-p/4086091
SIMULATIONNavigate to https://dev.azure.com, select Start Free, and specify the following credentials:User: User1-12345678@ExamUsers.comPassword: 0123456789Use the default setting to sign up for Azure DevOps and create an Azure DevOps organization. Once the organization is created, create a private project named Project1.You need to add an external user that has an email address of User2-12345678@ExamUsers.com as a stakeholder of the User1-12345678 Azure DevOps organization.The user must be added to the most restrictive Azure DevOps group.To complete this task, sign in to the Azure DevOps portal as User1-12345678@ExamUsers.com.
Phase 1: Create an organizationAzure DevOps, Create an organizationStep 1: Sign in to Azure DevOps.Step 2: Select New organization.Step 3: Confirm information, and then select Continue.Congratulations, you're an organization owner!Phase 2: Create a Private projectCrate a project in Azure DevOpsStep 4: Sign in to your organization (https://dev.azure.com/{yourorganization}).Step 5: Select New project.Step 6: Enter information into the form provided.Provide a name for your project. [Enter Project1]Choose the visibility, initial source control type, and work item process. [Select Private]Step 7: Select Create. Azure DevOps displays the project welcome page.Phase 3: Add an external userAzure DevOps, Add external users to your organizationInvite external userStep 8: Sign in to your organization (https://dev.azure.com/{yourorganization}).Step 9: Select gear icon Organization settings.Step 10: Select Users, and then select Add users.Step 11: Enter information based on the following guidance, and then select Add.Users: Enter the email address for the user. [Enter User2-12345678@ExamUsers.com]
https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/create-organization https://learn.microsoft.com/en-us/azure/devops/organizations/projects/create-project https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/add-external-user
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.
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
Share your comments for Microsoft AZ-400 exam with other users:
Question 2:
This is very good and accurate. Explanation is very helpful even thou some are not 100% right but good enough to pass.