Correct Answer:

Explanation:

Box 1: Modify ApplicationInsights.config

In ApplicationInsights.config, you can adjust several parameters in the AdaptiveSamplingTelemetryProcessor node. The figures shown are the default values:

5

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.

00:00:15

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 sampling Use 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 detection Proactive 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 Export Want 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.

Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/app/sampling https://docs.microsoft.com/en-us/azure/azure-monitor/app/devops#smart-detection

Correct Answer:

Box 1: Get-AzResource Use the following command to examine the access control mode for all workspaces in the subscription: PowerShell Get-AzResource -ResourceType Microsoft.OperationalInsights/workspaces -ExpandProperties | foreach {$_.Name + ": " + $_.Properties.features.enableLogAccessUsingOnlyResourcePermissions

Box 2: -ResourceType Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/logs/manage-access

Correct Answer:

Step 1: Create a NuGet package.

NuGet and Maven are public package managers that support multiple feeds.

Step 2: Create an Azure Artifacts feed that uses upstream sources If you want to use packages from multiple feeds, use upstream sources to bring packages from multiple feeds together into a single feed. Step 3: Create a Micrtosoft Visual

Studio project that includes all the packages Consume NuGet packages from upstream sources: Now you can open Visual Studio and install packages from the upstream sources you just configured.

Correct Answer:

Correct Answer:

Correct Answer: AB

References: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops

Correct Answer: B

Correct Answer: B

Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/insights/azure-sql

Correct Answer: D

Reference: https://docs.github.com/en/code-security/secret-scanning/secret-scanning-partner-program

Correct Answer: B

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.

You can also enter a commit or pull request message to transition the work item. The system will recognize fix, fixes, fixed and apply it to the #-mention item that follows.

Example:

Fixes AB#123, AB#124, and AB#126 Links to Azure Boards work items 123, 124, and 126. Transitions only the first item, 123 to the Resolved workflow state category or, if none is defined, then the Completed workflow state category.

Reference:

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