Microsoft Designing and Implementing Microsoft DevOps Solutions (AZ-400 Korean Version) - AZ-400 Korean FREE EXAM DUMPS QUESTIONS & ANSWERS

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).

Explanation:

Explanation:

Box 1: requests
Failed requests (requests/failed):
The count of tracked server requests that were marked as failed.
Kusto code:
requests
| where success == ' False '
Box 2: success == false
Reference:
https://docs.microsoft.com/en-us/azure/azure-mon itor/ platform/app-insights-metrics

See explanation below
Explanation:
Step 1: Understand the Requirements
* You need to create a self-hosted agent for Azure Pipelines.
* It will be hosted in a pod (for example, in Kubernetes).
* All pipelines in Project1 should be able to use this agent pool named Pool1 .
Step 2: Create the Agent Pool in Azure DevOps
* Go to your Azure DevOps organization : https://dev.azure.com/{YourOrganizationName}
* In the bottom-left corner, click on the Organization settings gear icon.
* In the left menu, click on Agent pools .
* Click on Add pool .
* Provide the following:
* Pool name: Pool1
* Pool type: Self-hosted
* Grant access permission to all pipelines: Checked (so that all Project1 pipelines can use this pool)
* Click Create .
Now you have an empty agent pool named Pool1 .
Step 3: Prepare the Self-hosted Agent as a Pod
You need to deploy an Azure Pipelines agent container as a pod . Here's how to do it:
Option 1: Using Kubernetes directly (YAML deployment)
* Create a Kubernetes deployment YAML file for the agent pod:
apiVersion: apps/v1
kind: Deployment
metadata:
name: azure-pipelines-agent
labels:
app: azure-pipelines-agent
spec:
replicas: 1
selector:
matchLabels:
app: azure-pipelines-agent
template:
metadata:
labels:
app: azure-pipelines-agent
spec:
containers:
- name: agent
image: mcr.microsoft.com/azure-pipelines/vsts-agent:latest
env:
- name: AZP_URL
value: " https://dev.azure.com/{YourOrganizationName} "
- name: AZP_TOKEN
valueFrom:
secretKeyRef:
name: azure-pipelines-token
key: token
- name: AZP_POOL
value: " Pool1 "
- name: AZP_AGENT_NAME
value: " agent-pod "
* Create a Kubernetes secret for the personal access token (PAT) :
kubectl create secret generic azure-pipelines-token --from-literal=token= < your-PAT > Note:
* Replace < your-PAT > with a PAT that has "Agent Pools (Read & manage)" scope.
* Replace {YourOrganizationName} with your actual Azure DevOps organization.
* Deploy the pod:
bash
Copy
kubectl apply -f azure-pipelines-agent.yaml
Step 4: Validate the Agent Connection
* Go back to Organization Settings > Agent pools > Pool1 in Azure DevOps.
* You should see the agent pod connected and listed as online .
Step 5: Use the Pool in Pipelines
By default, all pipelines in Project1 will now have access to the Pool1 agent pool because you granted access during the pool creation.
In your pipeline YAML files, specify the pool name to use the self-hosted agent:
yaml
Copy
pool:
name: Pool1

Explanation:
Graphical user interface, text, application Description automatically generated

Woodgrove Bank identifies the following technical requirements:
* The Azure DevOps dashboard must display the metrics shown in the following table:

Box 1: Velocity
Velocity displays your team velocity. It shows what your team delivered as compared to plan.
Box 2: Release pipeline overview
Release pipeline overview shows the status of environments in a release definition.
Box 3: Query tile
Query tile displays the total number of results from a query.
Reference:
https://docs.micros oft.com/en-us/azure/devops/report/dashboards/widget-catalog?view=azure-devops

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).

Explanation:

Explanation:

Step 1: Create an agent pool
Azure Pipelines provides a pre-defined agent pool named Azure Pipelines with Microsoft-hosted agents.
Step 2: Create a deployment group
Deployment groups make it easy to define logical groups of target machines for deployment, and install the required agent on each machine.
Step 3: Execute the Azure Pipelines Agent extension to the virtual machines Install the Azure Pipelines Agent Azure VM extension Step 4: Add and configure a deployment group job for the pipeline Tasks that you define in a deployment group job run on some or all of the target servers, depending on the arguments you specify for the tasks and the job itself.
Reference:
https://docs.m icrosoft.com/en-us/azure/devops/pipelines /release/deployment-groups/howto -provisi on-deployment-group-agen ts

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).

Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).