AZ-400 Online Practice Questions and Answers

Correct Answer:

Step 1: Kubectl create

You can add a service account to Tiller using the --service-account flag while you’re configuring Helm (step 2 below). As a prerequisite, you’ll have to create a role binding which specifies a role and a service account name that have

been set up in advance.

Example: Service account with cluster-admin role

$ kubectl create -f rbac-config.yaml

serviceaccount "tiller" created

clusterrolebinding "tiller" created

$ helm init --service-account tiller

Step 2: helm init

To deploy a basic Tiller into an AKS cluster, use the helm init command.

Step 3: helm install

To install charts with Helm, use the helm install command and specify the name of the chart to install.

References:

https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm

https://docs.helm.sh/using_helm/#tiller-namespaces-and-rbac

Correct Answer:

Explanation:

Box 1: - 'releases/**'

Scan on pull requests to any branch that has a prefix of releases/.

Note: You can use special characters in path, branch, and tag filters.

*: Matches zero or more characters, but does not match the / character. For example, Octo* matches Octocat.

**: Matches zero or more of any character.

Box 2: - 'src/**'

Scan all the files in the subdirectories of the src directory.

Use the paths filter when you want to include file path patterns or when you want to both include and exclude file path patterns.

Box 3: - '**/*.md'

Exclude scanning of markdown files.

Use the paths-ignore filter when you only want to exclude file path patterns.

Reference:

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet

Correct Answer:

JIRA: Release pipelines Atlassian's Jira Software is a popular application that helps teams to plan, track, and manage software releases, whereas Octopus Deploy helps teams automate their development and operations processes in a fast, repeatable, and reliable manner. Together, they enable teams to get better end-to-end visibility into their software pipelines from idea to production.

Jenkins: Repos One way to integrate Jenkins with Azure Pipelines is to run CI jobs in Jenkins separately. This involves configuration of a CI pipeline in Jenkins and a web hook in Azure DevOps that invokes the CI process when source code is pushed to a repository or a branch.

Octopus: Build pipelines

References: https://octopus.com/blog/octopus-jira-integration

https://www.azuredevopslabs.com/labs/vstsextend/jenkins/

Correct Answer:

Step 1: Create a repository

A Git repository, or repo, is a folder that you've told Git to help you track file changes in. You can have any number of repos on your computer, each stored in their own folder.

Step 2: Create a branch

Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management standards.

Step 3: Add a build validation policy

When a build validation policy is enabled, a new build is queued when a new pull request is created or when changes are pushed to an existing pull request targeting this branch. The build policy then evaluates the results of the build to

determine whether the pull request can be completed.

Scenario:

Implement a code flow strategy for Project2 that will:

Enable Team2 to submit pull requests for Project2.

Enable Team2 to work independently on changes to a copy of Project2.

Ensure that any intermediary changes performed by Team2 on a copy of Project2 will be subject to the same restrictions as the ones defined in the build policy of Project2.

References: https://docs.microsoft.com/en-us/azure/devops/repos/git/manage-your-branches

Correct Answer: A

Reference: https://www.azuredevopslabs.com/labs/vstsextend/whitesource/

Correct Answer: B

Correct Answer: BD

Correct Answer: CE

https://docs.microsoft.com/en-us/azure/security-center/features-paas

Correct Answer: ACD

Create an Azure Resource Manager service connection with an existing service principal

AB: Enter the information about your service principal into the Azure subscription dialog textboxes:

1.

Tenant ID

2.

Subscription ID

3.

Subscription name

4.

Service principal ID

Either the service principal client key or, if you have selected Certificate, enter the contents of both the certificate and private key sections of the *.pem file.

If you're using the classic editor, select data you need. For example, the App service name.

If you're using YAML, then go to the resource in the Azure portal, and then copy the data into your code. For example, to deploy a web app, you would copy the name of the App Service into the WebAppName value.

Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/library/connect-to-azure

Correct Answer: C

WhiteSource provides WhiteSource Bolt, a lightweight open source security and management solution developed specifically for integration with Azure DevOps and Azure DevOps Server.

Note: WhiteSource is the leader in continuous open source software security and compliance management. WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source repositories.

Note: Blackduck would also be a good answer, but it is not an option here.

Reference: https://www.azuredevopslabs.com/labs/vstsextend/whitesource/