AZ-400 Online Practice Questions and Answers

Correct Answer:

Box 1: TimeGenerated>ago(7d)

Example:

// Find all processes that started in the last 3 days. ID 4688: A new process has been created.

let RunProcesses = SecurityEvent

| where TimeGenerated > ago(3d)

| where EventID == “4688”;

Box 2: bin(TimeGenerated, 1h)

Example:

// Find the 5 processes that were run the most

let Top5Processes =

RunProcesses

| summarize count() by Process | top 5 by count_; // Create a time chart of these 5 processes – hour by hour RunProcesses | where Process in (Top5Processes) | summarize count() by bin (TimeGenerated, 1h), Process | render timechart Reference:

https://marckean.com/2019/03/25/log-analytics-advanced-queries/

Correct Answer:

Step 1: Create a dependency graph for the application

By linking work items and other objects, you can track related work, dependencies, and changes made over time. All links are defined with a specific link type. For example, you can use Parent/Child links to link work items to support a

hierarchical tree structure. Whereas, the Commit and Branch link types support links between work items and commits and branches, respectively.

Step 2: Group the related components.

Packages enable you to share code across your organization: you can compose a large product, develop multiple products based on a common shared framework, or create and share reusable components and libraries.

Step 3: Assign ownership to each component graph

References:

https://docs.microsoft.com/en-us/azure/devops/boards/queries/link-work-items-support-traceability?view=azure-devopsandtabs=new-web-form

https://docs.microsoft.com/en-us/visualstudio/releasenotes/tfs2017-relnotes

Correct Answer:

Box 1: Burndown chart

Bottlenecks in the software development process

Interpret a burndown or burnup chart

Your 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 time

How long it takes to close a work item after the item was started

Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.

Box 3: Sprint burndown

A burndown chart for the work in a single iteration

The 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:

*

Velocity

Velocity 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 time

Lead time measures the total time elapsed from the creation of work items to their completion.

Reference: 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

Correct Answer: D

Correct Answer: B

References: https://marketplace.visualstudio.com/items?itemName=ms.vss-exploratorytesting-web

Correct Answer: A

In Visual Designer you enable continuous integration (CI) by:

1.

Select the Triggers tab.

2.

Enable Continuous integration.

A continuous integration trigger on a build pipeline indicates that the system should automatically queue a new build whenever a code change is committed.

References:

https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-designer

Correct Answer: B

Create a service hook for Azure DevOps with Slack to post messages to Slack in response to events in your Azure DevOps organization, such as completed builds, code changes, pull requests, releases, work items changes, and more. Note:

1. Go to your project Service Hooks page: https://{orgName}/{project_name}/_settings/serviceHooksSelect Create Subscription.

3.

Choose the types of events you want to appear in your Slack channel.

4.

Paste the Web Hook URL from the Slack integration that you created and select Finish.

5.

Now, when the event you configured occurs in your project, a notification appears in your team's Slack channel.

Reference: https://docs.microsoft.com/en-us/azure/devops/service-hooks/services/slack

Correct Answer: A

Reference: https://octopus.com/docs/packaging-applications

Correct Answer: B

Link GitHub commits, pull requests, and issues to work items in Azure Boards

Use AB# mention to link from GitHub to Azure Boards work items

From a GitHub commit, pull request or issue, use the following syntax to create a link to your Azure Boards work item. Enter the AB#ID within the text of a commit message. Or, for a pull request or issue, enter the AB#ID within the title or

description (not a comment).

AB#{ID}

For example, AB#125 will link to work item ID 125.

Reference:

https://learn.microsoft.com/en-us/azure/devops/boards/github/link-to-from-github

Correct Answer: B