Design and implement build and release pipelines practice questions

The deployment slot is not configured correctly.

Why wrong: Slot configuration does not directly cause file lock errors.

The Azure App Service plan is not scaled appropriately.

Why wrong: Scaling does not cause file lock errors.

The build configuration is set to Release instead of Debug.

Why wrong: Build configuration does not affect deployment file locks.

Use a single release pipeline that triggers manual deployment for each service.

Why wrong: Manual deployment is not scalable.

Create a single build pipeline that builds all services together to ensure consistency.

Why wrong: Single pipeline reduces independence and scalability.

Build each service separately, but skip integration tests to avoid complexity.

Why wrong: Integration tests are important for microservices.

Configure branch policy to require a pull request for documentation changes.

Why wrong: Branch policy does not prevent pipeline trigger.

Add a 'condition' to the pipeline that checks if changed files are documentation.

Why wrong: Condition does not prevent the pipeline from being triggered.

Disable CI trigger and rely on scheduled builds.

Why wrong: Scheduled builds may miss important changes.

Use a separate release pipeline that deploys to a production environment for testing.

Why wrong: Testing in production is risky.

Use a single release pipeline that deploys to a staging slot and runs tests on the slot.

Why wrong: Slots are not destroyed after tests.

Run integration tests in the build pipeline using a mock environment.

Why wrong: Mocks do not represent real environment.

Use a variable group without Key Vault integration for easier management.

Why wrong: Without Key Vault, secrets are less secure.

Store secrets directly in the YAML pipeline file.

Why wrong: Hardcoding secrets is insecure.

Disable CI triggers to reduce exposure.

Why wrong: CI triggers do not directly affect secret security.

The policy blocks the pipeline from running if fewer than two reviewers approve.

Why wrong: The effect is audit, not deny.

The policy requires two reviewers and blocks the pipeline if not met.

Why wrong: No blocking effect.

The policy does not apply to build pipelines because the field type is teamProjects.

Why wrong: The policy applies but with audit effect.

Keep the single pipeline but add caching for dependencies.

Why wrong: Caching helps but the pipeline still builds all services.

Use a single pipeline but add conditional stages to skip unchanged services.

Why wrong: Conditional stages still require evaluation and may not effectively skip.

Create separate pipelines for each service with path triggers, and disable the comprehensive pipeline.

Why wrong: Integration tests across services would be missed.

Use a `deployment: Staging` job with `displayName: Deploy to staging`.

Why wrong: While a deployment job is correct, the option incorrectly combines deployment and displayName; the deployment job type is specified by `deployment: Staging`, but the displayName is not the issue; the option is plausible but the correct configuration must include a deployment job, not a build job. However, option E is not precise enough and could be misleading; it is not the best answer compared to A and D.

Add `condition: succeeded()` to the build job.

Why wrong: The condition should be on the deployment stage, not the build job, and it should reference the test stage.

Define the trigger in the `resources` section using `pipelines`.

Why wrong: Pipeline triggers are set at the root level, not in resources.

The pipeline does not trigger because the `docs/` path is excluded and includes a change.

Why wrong: The pipeline triggers because there is also a change in src/, which is not excluded.

The pipeline triggers only if the change is on a branch matching `release/*`.

Why wrong: The trigger includes main as well, so changes to main also trigger the pipeline.

The pipeline triggers but runs only tests because the build is skipped due to excluded paths.

Why wrong: Excluded paths only affect triggering; if the pipeline triggers, all steps run unless conditions specify otherwise.

Set the connection string as a secret variable in the pipeline UI and reference it in the integration test step.

Why wrong: Hardcoding secrets in the pipeline UI is insecure and not a best practice; secrets should be fetched from Key Vault at runtime.

Add a variable group linked to the Key Vault and reference the secret variable directly in the integration test step.

Why wrong: While variable groups can link to Key Vault, this requires additional setup in the library and is less flexible for just one secret; the task is more direct.

Use a PowerShell script to read the secret from Key Vault using the service principal.

Why wrong: While possible, it's more complex and error-prone than using the built-in Key Vault task, which handles authentication and variable mapping.

Use the 'canary' strategy with manual intervention

Why wrong: Canary strategy does not automatically roll back; it requires manual approval or additional steps.

Use the 'blueGreen' strategy and configure automatic swap

Why wrong: BlueGreen strategy requires manual swap; it does not roll back automatically.

Use the 'runOnce' strategy with a rollback task

Why wrong: runOnce does not support automatic rollback; you would need custom scripting.

and(succeeded(), startsWith(variables['Build.SourceBranchName'], 'v'))

Why wrong: Build.SourceBranchName for a tag is the tag name, so this would also work but is less precise; however, the official documentation recommends using Build.SourceBranch.

and(succeeded(), startsWith(variables['Build.SourceVersion'], 'v'))

Why wrong: Build.SourceVersion is the commit SHA, not the tag.

and(succeeded(), eq(variables['Build.Reason'], 'IndividualCI'))

Why wrong: Build.Reason checks for CI trigger, not tag.

Add 'approvals: Production' to the deployment job

Why wrong: 'approvals' is not a valid keyword in YAML pipeline syntax.

Add 'checks: Production' to the deployment job

Why wrong: 'checks' is not a valid keyword; checks are configured on environments.

Add 'dependsOn: ProductionApproval' and use a separate stage for approval

Why wrong: While you can create a separate stage for approval, it's not the standard way; environment approvals are built-in.

Azure App Service manage: Delete staging slot

Why wrong: Deleting the staging slot is not part of the swap process.

Azure CLI: Run az webapp deployment slot swap

Why wrong: While this works, it's not a built-in task; the question expects Azure App Service tasks.

In the Deploy stage, set 'condition: and(succeeded('Build'), succeeded('Test'))'

Why wrong: This syntax is for job conditions; stage conditions do not accept string arguments for succeeded().

In the Deploy stage, set 'dependsOn: [Build, Test]' and 'condition: stageDependencies.Build.result == 'Succeeded''

Why wrong: 'stageDependencies' is not a valid expression; you would use 'dependencies.Build.result'.

NuGetToolInstaller@1

Why wrong: This installs NuGet, not the .NET SDK.

DotNetCoreCLI@2

Why wrong: This runs .NET commands but does not install a specific SDK version.

PowerShell@2

Why wrong: PowerShell can install SDK but it's not the built-in task for this purpose.

Add a post-deployment approval on the staging stage.

Why wrong: Post-deployment happens after deployment, not before.

Configure a deployment gate with a manual intervention task.

Why wrong: Gates evaluate conditions, but manual approval is simpler and more direct.

Use a pipeline decorator to inject approval step.

Why wrong: Decorators are for injecting steps, not for approvals.

Use the NuGetCommand@2 task with the -Cache argument.

Why wrong: NuGetCommand does not have a -Cache argument for cross-build caching.

Set the NUGET_PACKAGES environment variable to a custom path and rely on pipeline caching plugin.

Why wrong: The environment variable is useful but caching must be explicitly configured.

Use the DotNetCoreCLI@2 task with the --no-restore flag and manually copy packages.

Why wrong: --no-restore skips restore, not caching.

condition: eq(variables['Build.SourceBranch'], 'main')

Why wrong: Missing 'refs/heads/' prefix, so it won't match.

condition: and(succeeded(), eq(variables['System.PullRequest.TargetBranch'], 'main'))

Why wrong: This checks PR target branch, not the source branch.

condition: ne(variables['Build.Reason'], 'PullRequest')

Why wrong: This excludes PRs but does not limit to main branch.