AZ-400 Continuous Integration 4

Question 1

What is the purpose of 'code coverage' metrics collected during a CI pipeline?

Accepted Answer

To report what percentage of source code is exercised by automated tests

Answer

Code coverage metrics indicate the proportion of production code executed by automated tests, helping teams identify untested code paths.

Question 2

A pipeline needs to pass a secret API key to a build script securely. What is the correct approach in Azure Pipelines?

Accepted Answer

Store the key as a secret pipeline variable and reference it with $(VariableName)

Answer

Secret pipeline variables are masked in logs and encrypted at rest; they are referenced the same way as regular variables but never exposed in output.

Question 3

Which Azure DevOps feature allows you to group related pipelines and share variables, service connections, and agent pools across them?

Accepted Answer

Pipeline libraries and variable groups

Answer

Variable groups in the Pipelines Library let you define shared variables and link Azure Key Vault secrets that can be referenced by multiple pipelines.

Question 4

What does 'shift-left testing' mean in the context of a CI/CD pipeline?

Accepted Answer

Performing tests earlier in the development lifecycle, closer to code authoring

Answer

Shift-left testing moves quality checks (unit tests, static analysis, security scans) earlier in the pipeline so defects are caught before later, more expensive stages.

Question 5

In Azure Pipelines, which condition expression causes a step to run only when the previous step fails?

Accepted Answer

condition: failed()

Answer

The failed() condition expression makes a step execute only when one or more preceding steps have failed, useful for cleanup or notification steps.

AZ-400 Practice Test

AZ-400 Practice Test

AZ-400 Continuous Integration 4