Microsoft AZ-400 Practice Test - Questions Answers, Page 4

Step 1: Kubectl create

You can add a service account to Tiller using the --service-account <NAME> 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

Box1: Private

In App Center, distribution groups are private by default. Only testers invited via email can access the releases available to this group.

Box 2: Public

Distribution groups must be public to enable unauthenticated installs from public links.

Box 3: Shared

Shared distribution groups are private or public distribution groups that are shared across multiple apps in a single organization.

Reference:

https://docs.microsoft.com/en-us/appcenter/distribution/groups

Deployment 1: Kubernetes.io/azure-file

You can use Azure Files to connect using the Server Message Block (SMB) protocol.

Deployment 2: Kubernetes.io/azure-disk

Deployment 3: azurekeyvault-flexvolume

azurekeyvault-flexvolume: Key Vault FlexVolume: Seamlessly integrate your key management systems with Kubernetes. Secrets, keys, and certificates in a key management system become a volume accessible to pods. Once the volume is mounted, its data is available directly in the container filesystem for your application.

Incorrect Answers:

blobfuse-flexvolume: This driver allows Kubernetes to access virtual filesystem backed by the Azure Blob storage.

References:

https://docs.microsoft.com/bs-cyrl-ba/azure/aks/azure-files-dynamic-pv

https://docs.microsoft.com/en-us/azure/aks/azure-disks-dynamic-pv

Step 1: Delete and recreate the repository.

Step 2: Add Config.json to the .gitignore file

Each line in the .gitignore excludes a file or set of files that match a pattern.

Example:

# ignore a single file

Config.json

Step 3: Run the get add .gitignore command

At the initial commit we want basically move from Untracked to Staged, for staging we have to indicate which file we want to move or specify a pattern, as example:

Reference:

http://hermit.no/how-to-find-the-best-gitignore-for-visual-studio-and-azure-devops/

https://geohernandez.net/how-to-add-an-existing-repository-into-azure-devops-repo-with-git/

Box 1; tag

Tagging. Like most VCSs, get has the ability to tag specific points in a repository’s history as being important. Typically, people use this functionality to mark release points (v1.0, v2.0 and so on).

Box 2: -a

Creating an annotated tag in get is simple. The easiest way is to specify -a when you run the tag command:

Example:

$ get tag -a v1.4 -m "my version 1.4"

Box 3: -m

Reference:

https://git-scm.com/book/en/v2/Git-Basics-Tagging

https://docs.microsoft.com/en-us/azure/key-vault/general/secure-your-key-vault

Step 1: Create a release pipeline

You need to create a new pipeline.

You can integrate Azure Resource Manager templates (ARM templates) with Azure Pipelines for continuous integration and continuous deployment (CI/CD).

Step 2: Add an Azure Resource Group Deployment task

Step 3: Set the template parameters

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/add-template-to-azure-pipelines

Box 1: 7

Box 2: web application artifact

Box 1: A deployment group

When authoring an Azure Pipelines or TFS Release pipeline, you can specify the deployment targets for a job using a deployment group. If the target machines are Azure VMs, you can quickly and easily prepare them by installing the Azure Pipelines Agent Azure VM extension on each of the VMs, or by using the Azure Resource Group Deployment task in your release pipeline to create a deployment group dynamically.

Box 2: A deployment group

References: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deployment-groups