Practice Free AZ-400 Exam Online Questions

Explanation:

You can use the combination of Terraform and Yeoman. Terraform is a tool for creating infrastructure on Azure. Yeoman makes it easy to create Terraform modules.

Terratest provides a collection of helper functions and patterns for common infrastructure testing tasks, like making HTTP requests and using SSH to access a specific virtual machine.

The following list describes some of the major advantages of using Terratest:

✑ Convenient helpers to check infrastructure – This feature is useful when you want to verify your real infrastructure in the real environment.

✑ Organized folder structure – Your test cases are organized clearly and follow the standard Terraform module folder structure.

Test cases are written in Go – Many developers who use Terraform are Go developers. If you’re a Go developer, you don’t have to learn another programming

✑ language to use Terratest.

✑ Extensible infrastructure – You can extend additional functions on top of Terratest, including Azure-speci c features.

Reference:

https: //docs.microsoft.com/en-us/azure/developer/terraform/create-base-template-using-yeoman

https: //docs.microsoft.com/en-us/azure/developer/terraform/test-modules-using-terratest

Explanation:

Step 1: az acr create

An Azure Container Registry (ACR) can also be created using the new Azure CLI. az acr create –name <REGISTRY_NAME>

–resource-group <RESOURCE_GROUP_NAME>

–sku Basic

Step 2: az ad sp create-for-rbac

Once the ACR has been provisioned, you can either enable administrative access (which is okay for testing) or you create a Service Principal (sp) which will provide a client_id and a client_secret. az ad sp create-for-rbac –scopes

/subscriptions/<SUBSCRIPTION_ID>/resourcegroups/<RG_NAME>/providers/Microsoft.ContainerRegistry/registries/<REGISTRY_NAME> –role Contributor

–name <SERVICE_PRINCIPAL_NAME>

Step 3: kubectl create

Create a new Kubernetes Secret.

kubectl create secret docker-registry <SECRET_NAME>

–docker-server <REGISTRY_NAME>.azurecr.io

–docker-email <YOUR_MAIL>

–docker-username=<SERVICE_PRINCIPAL_ID>

–docker-password <YOUR_PASSWORD>

Reference: https: //thorsten-hans.com/how-to-use-private-azure-container-registry-with-kubernetes

Explanation:

Step 1: Create a YAML file.

If your AKS cluster is RBAC-enabled, you must create a service account and role binding for use with Tiller. To create a service account and role binding, create a file named rbac-virtual-kubelet.yaml

Step 2: Run kubectl apply.

Apply the service account and binding with kubectl apply and specify your rbac-virtual-kubelet.yaml file.

Step 3: Run helm init.

Configure Helm to use the tiller service account:

helm init –service-account tiller

You can now continue to installing the Virtual Kubelet into your AKS cluster.

References: https: //docs.microsoft.com/en-us/azure/aks/virtual-kubelet

Explanation:

Step 1: Create a YAML file.

If your AKS cluster is RBAC-enabled, you must create a service account and role binding for use with Tiller. To create a service account and role binding, create a file named rbac-virtual-kubelet.yaml

Step 2: Run kubectl apply.

Apply the service account and binding with kubectl apply and specify your rbac-virtual-kubelet.yaml file.

Step 3: Run helm init.

Configure Helm to use the tiller service account:

helm init –service-account tiller

You can now continue to installing the Virtual Kubelet into your AKS cluster.

References: https: //docs.microsoft.com/en-us/azure/aks/virtual-kubelet

Explanation:

Defining the Release Pipeline

Once the application portion of the Release pipeline has been configured, the security scan portion can be defined. In our example, this consists of 8 tasks, primarily using the Azure CLI task to create and use the ACI instance (and supporting structures). Otherwise specified, all the Azure CLI tasks are Inline tasks, using the default configuration options.

Reference: Questionhttps: //devblogs#49.microsoft.com/premier-developer/azure-devops-pipelines-leveraging-owasp-zap-in-the-release-pipeline/

Explanation:

Defining the Release Pipeline

Once the application portion of the Release pipeline has been configured, the security scan portion can be defined. In our example, this consists of 8 tasks, primarily using the Azure CLI task to create and use the ACI instance (and supporting structures). Otherwise specified, all the Azure CLI tasks are Inline tasks, using the default configuration options.

Reference: Questionhttps: //devblogs#49.microsoft.com/premier-developer/azure-devops-pipelines-leveraging-owasp-zap-in-the-release-pipeline/

Explanation:

Box 1: 5 minutes

The alert must calculate the average once every minute.

Note: We [Microsoft] recommend choosing an Aggregation granularity (Period) that is larger than the Frequency of evaluation, to reduce the likelihood of missing the first evaluation of added time series

Box 2: Static

Box 3: Greater than

Example, say you have an App Service plan for your website. You want to monitor CPU usage on multiple instances running your web site/app.

You can do that using a metric alert rule as follows:

✑ Target resource: myAppServicePlan

✑ Metric: Percentage CPU

✑ Condition Type: Static

✑ Dimensions

✑ Instance = InstanceName1, InstanceName2

✑ Time Aggregation: Average

✑ Period: Over the last 5 mins

✑ Frequency: 1 min

✑ Operator: GreaterThan

✑ Threshold: 70

✑ Like before, this rule monitors if the average CPU usage for the last 5 minutes exceeds 70%.

✑ Aggregation granularity

Reference: https: //docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-metric-overview