- (Exam Topic 4)
You are developing an open source solution that uses a GitHub repository. You create a new public project in Azure DevOps.
You plan to use Azure Pipelines for continuous build. The solution will use the GitHub Checks API. Which authentication type should you use?
Correct Answer:
C
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml https://developer.github.com/v3/checks/
- (Exam Topic 4)
You use Exabeam Fusion SIEM and the Azure cloud platform.
You need to integrate Exabeam and Azure. The solution must use OAuth authentication.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Solution:
Graphical user interface, text, application, email Description automatically generated
Does this meet the goal?
Correct Answer:
A
- (Exam Topic 4)
You have an app named App1. You have a Log Analytics workspace named Workspace 1 that contains two tables named Events and Logs. Appl manages events in multiple locations and writes logs to Workspace1.
You need to query Workspace1 for all log entries related to Asia that occurred during the last two days. In which order should you arrange the query statements? To answer, move all statements from the list of
statements to the answer area and arrange them in the correct order.
Solution:
Does this meet the goal?
Correct Answer:
A
- (Exam Topic 4)
Your company uses a Git repository in Azure Repos lo manage the source code of a web application. The master branch is protected from direct updates. Developers work on new features in the topic branches.
Because of the high volume of requested features, it is difficult to follow the history of the changes to the master branch.
You need to enforce a pull request merge strategy. The strategy must meet the following requirements:
• Consolidate commit histories
• Merge tie changes into a tingle commit
Which merge strategy should you use in the branch policy?
Correct Answer:
C
Squash merging is a merge option that allows you to condense the Git history of topic branches when you complete a pull request. Instead of each commit on the topic branch being added to the history of the default branch, a squash merge takes all the file changes and adds them to a single new commit on the default branch.
A simple way to think about this is that squash merge gives you just the file changes, and a regular merge gives you the file changes and the commit history.
Note: Squash merging keeps your default branch histories clean and easy to follow without demanding any workflow changes on your team. Contributors to the topic branch work how they want in the topic branch, and the default branches keep a linear history through the use of squash merges. The commit history of a master branch updated with squash merges will have one commit for each merged branch. You can step through this history commit by commit to find out exactly when work was done.
References: https://docs.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash
- (Exam Topic 4)
Your company deploys applications m Docket containers.
You want to detect known exploits in the Docket images used to provision the Docker containers.
You need to integrate image scanning into the application lifecycle. The solution must expose the exploits as early as possible during the application lifecycle.
What should you configure?
Correct Answer:
C
You can use the Docker task to sign into ACR and then use a subsequent script to pull an image and scan the container image for vulnerabilities.
Use the docker task in a build or release pipeline. This task can be used with Docker or Azure Container registry.
References:
https://docs.microsoft.com/en-us/azure/devops/articles/security-validation-cicd-pipeline?view=vsts
