Previous

Next

Knowledge check

Completed

Consider the following pipeline definition and pipeline template:

azure-pipelines.yml:

trigger: none

pool:
  vmImage: ubuntu-latest

stages:

- template: deploy.yml
  parameters:
    environmentName: Sandbox

- template: deploy.yml
  parameters:
    environmentName: Production

deploy.yml:

parameters:
- name: environmentName
  type: string

stages:
- stage: Deploy
  jobs:
  - job: Deploy
    steps:
    - checkout: self
    - task: AzureCLI@2
      name: DeployBicepFile
      displayName: Deploy Bicep file
      inputs:
        azureSubscription: SharedServiceConnection
        scriptType: 'bash'
        scriptLocation: 'inlineScript'
        inlineScript: |
            az deployment group create \
            --name $(Build.BuildNumber) \
            --resource-group ${{parameters.environmentName}}_rg \
            --template-file deploy/main.bicep \
            --parameters deploy/parameters.${{parameters.environmentName}}.json

The Git repository's deploy folder also contains the Bicep file and parameter files.

1.

When you try to run the pipeline, Azure Pipelines gives you an error. What's the most likely cause of the problem?

The identifier of each stage isn't unique.

The trigger property is set to none.

The ubuntu-latest agent pool name isn't valid.

2.

How can you improve the security of this pipeline?

Use separate service connections for each environment.

Add a condition to deploy only when the environment name is Production.

Create a new Azure role definition.

3.

You need to add a new environment named Integration to the pipeline. Which of these actions should you take as part of adding the new environment?

Add a new pipeline file.

Add a new pipeline template file.

Add a new Bicep parameters file.

4.

You need to add a new parameter to your deployment that contains a connection string and password to access a database. Which of these approaches should you consider?

Define a variable in the azure-pipelines.yml file.

Define a variable group in the Azure Pipelines web interface and mark the variable as secret.

Add the parameter to the parameters.ENVIRONMENT_NAME.json files.

You must answer all questions before checking your work.

Continue