- (Topic 4)
You have an Azure DevOps project that contains a release pipeline and a Git repository. When a new code revision is committed to the repository, a build and release is triggered.
You need to ensure that release information for the pipeline is added automatically to the work items associated to the Get commit.
What should you do?
Correct Answer:
A
Service hooks in Azure DevOps allow you to trigger actions in other tools based on events that occur in your Azure DevOps project. To automatically add release information to work items associated with a Get commit, you would need to configure a service hook that listens for commit events in your Get repository, and then sends the release information to the appropriate work items.
Here's the steps you can follow to set up a service hook for this purpose:
✑ In your Azure DevOps project, navigate to the project settings by clicking on the gear icon in the top right corner of the page.
✑ Select "Service Hooks" from the left-hand menu.
✑ Click on the "New Subscription" button to create a new service hook.
✑ In the "Event" drop-down menu, select "Code pushed" to trigger the service hook when a new code revision is committed to the repository.
✑ In the "Actions" section, select the action that you want to take place when the service hook is triggered. For example, you might use the "Link work items to commits" action to automatically associate work items with the relevant commits.
✑ Configure the remaining settings as needed, and then click on the "Create" button to create the service hook.
You can find more information on Service hooks in Azure DevOps by following this link https://docs.microsoft.com/en-us/azure/devops/service-hooks/overview?view=azure- devops
SIMULATION - (Topic 4)
You have several apps that use an Azure SQL Database named db1.
You need to ensure that queries to db1 are tuned by Azure over time. The solution must only apply to db1.
To complete this task, sign in to the Microsoft Azure portal.
Solution:
* 1. To enable automatic tuning on a single database, navigate to the database in the Azure portal and select Automatic tuning.
* 2. Select the automatic tuning options you want to enable and select Apply.
Note: Individual automatic tuning settings can be separately configured for each database. You can manually configure an individual automatic tuning option, or specify that an option inherits its settings from the server.
Does this meet the goal?
Correct Answer:
A
- (Topic 4)
You have an Azure DevOps organization named Contoso and art Azure subscription The subscription contains an Azure virtual machine scale set named VMSS1 that is configured for autoscaling.
You use Azure DevOps to build a web app named Appl and deploy Appl to VMSS1. Appl is used heavily and has usage patterns that vary on a weekly basis.
You need to recommend a solution to detect an abnormal rise in the rate of failed requests to Appl. The solution must minimize administrative effort.
What should you include in the recommendation?
Correct Answer:
C
After setting up Application Insights for your project, and if your app generates a certain minimum amount of data, Smart Detection of failure anomalies takes 24 hours to learn the normal behavior of your app, before it is switched on and can send alerts.
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/proactive-failure-diagnostics
HOTSPOT - (Topic 4)
Your company uses a Git source-code repository.
You plan to implement GitFlow as a workflow strategy.
You need to identify which branch types are used for production code and preproduction code in the strategy.
Which branch type should you identify for each code type? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Solution:
Box 1: Master
The Master branch contains production code. All development code is merged into master in sometime.
Box 2: Develop
The Develop branch contains pre-production code. When the features are finished then they are merged into develop.
Does this meet the goal?
Correct Answer:
A
DRAG DROP - (Topic 1)
Which package feed access levels should be assigned to the Developers and Team Leaders groups for the investment planning applications suite? To answer, drag the appropriate access levels to the correct groups. Each access level 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.
Solution:
Box 1: Reader
Members of a group named Developers must be able to install packages.
Feeds have four levels of access: Owners, Contributors, Collaborators, and Readers. Owners can add any type of identity-individuals, teams, and groups-to any access level.
Box 2: Owner
Members of a group named Team Leaders must be able to create new packages and edit the permissions of package feeds.
Does this meet the goal?
Correct Answer:
A
