Release pipeline basics in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding artifact sources in Azure release pipelines

In an Azure release pipeline, what happens when you configure multiple artifact sources?

A The pipeline triggers when any one of the artifact sources has a new version available.

B The pipeline triggers only when all artifact sources have new versions available.

C The pipeline ignores artifact sources and triggers manually only.

D The pipeline triggers only if the primary artifact source has a new version, ignoring others.

💡 Hint

Think about how pipelines react to changes in any input source.

Azure release pipelines trigger when any configured artifact source has a new version. This allows the pipeline to react to changes from multiple sources independently.

❓ Architecture

intermediate

Stages and approvals in release pipelines

Which statement best describes the role of stages and approvals in an Azure release pipeline?

A Stages define deployment steps; approvals are manual gates before or after stages to control flow.

B Stages are manual checkpoints; approvals automatically deploy to next environment.

C Approvals replace stages and automate all deployment steps.

D Stages and approvals are unrelated and used for different pipelines.

💡 Hint

Consider how deployment steps and manual checks work together.

Stages represent deployment phases like Dev, Test, Prod. Approvals are manual gates that pause the pipeline before or after stages to ensure human review.

❓ security

advanced

Securing secrets in release pipelines

Which method is the most secure way to handle sensitive information like passwords in Azure release pipelines?

A Hardcode secrets in the application code deployed by the pipeline.

B Embed secrets in scripts within the pipeline YAML file.

C Store secrets directly in pipeline variables marked as secret.

D Use Azure Key Vault and link it to the pipeline to fetch secrets at runtime.

💡 Hint

Think about centralized secret management and runtime retrieval.

Using Azure Key Vault linked to the pipeline ensures secrets are stored securely and accessed only at runtime, reducing exposure risk.

❓ Configuration

advanced

Pipeline variable scopes and overrides

Given a variable named connectionString defined at both pipeline and stage levels, which value is used during deployment in that stage?

A The variable is ignored and must be passed manually.

B The stage-level <code>connectionString</code> value overrides the pipeline-level value for that stage.

C Both values are merged and concatenated during deployment.

D The pipeline-level <code>connectionString</code> value is always used.

💡 Hint

Consider how variable scopes work in layered configurations.

Stage-level variables override pipeline-level variables for that stage, allowing environment-specific customization.

✅ Best Practice

expert

Optimizing release pipeline deployment speed

You want to speed up deployments in a release pipeline that has multiple independent stages. Which approach achieves this best?

A Configure stages to run sequentially, one after another.

B Add manual approvals between every stage to ensure quality.

C Configure stages to run in parallel where dependencies allow.

D Combine all stages into a single stage to reduce overhead.

💡 Hint

Think about how tasks can run at the same time safely.

Running independent stages in parallel reduces total deployment time while maintaining separation and control.