Select Two (Multi-Select) Questions

Set up a webhook in Azure Repos to call Azure Logic Apps on pull request merge.

Why wrong: Webhooks require custom logic, not a built-in integration.

Configure a Service Hooks subscription in Azure DevOps to send pull request merge events to Azure Boards.

Why wrong: Service Hooks send events to external systems, not directly update work items.

Create an Azure Function that listens for pull request merge events and updates work items via the REST API.

Why wrong: This is a custom solution, not a built-in configuration.

Reduced risk of configuration drift

Why wrong: Multiple repos can also have configuration management; monorepo doesn't inherently reduce drift.

Faster clone times due to smaller repository size

Why wrong: Monorepos are typically larger, leading to slower clones.

Configure the service connection to only allow deployments with tags.

Why wrong: Service connections don't enforce tagging.

Create an Azure Policy with the 'audit' effect to report non-compliant resources.

Why wrong: Audit only reports, does not enforce.

Configure a branch policy on the main branch to require tag verification in pull requests.

Why wrong: Branch policies do not affect Azure resource deployment.

Aggregate telemetry into 1-minute buckets before sending

Why wrong: Application Insights does not accept pre-aggregated telemetry.

Set a maximum telemetry throughput limit on the Application Insights instance

Why wrong: No such limit setting exists.

Unit test framework

Why wrong: Unit tests are a good practice but not a prerequisite.

Docker container registry

Why wrong: Docker is not required for .NET Core; it can be deployed directly.

Scheduled trigger

Why wrong: Scheduled triggers run at specified times, not on PR creation.

Continuous integration trigger

Why wrong: CI triggers run on commits, not PRs.

Pipeline completion trigger

Why wrong: Pipeline completion triggers run when another pipeline completes, not on PR creation.

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.

Configure stage filters in the triggers section

Why wrong: Stage filters are for triggers, not conditions within a pipeline.

Use dependency conditions like 'succeededOrFailed'

Why wrong: Dependency conditions are built-in for run order, not for custom conditional logic.

Add a PowerShell script to check environment

Why wrong: While possible, it's not a pipeline-native strategy; the question asks for valid strategies in YAML.

Stop the web app before deploying, then start it after

Why wrong: Stopping the app causes downtime.

Deploy to all regions simultaneously

Why wrong: Simultaneous deployment can cause full outage if something goes wrong.

Use a single deployment slot for all regions

Why wrong: A single slot doesn't allow zero-downtime swap.

Use squash merge when completing pull requests to main.

Why wrong: Squash merge is optional; it simplifies history but is not required for build validation.

Create feature branches from main and keep them long-lived for stability.

Why wrong: Long-lived branches contradict the short-lived branch strategy.

Allow developers to commit directly to main for urgent fixes.

Why wrong: Direct commits bypass the pull request process and branch policy.

Enable the Live Metrics Stream feature in Application Insights.

Why wrong: Live Metrics Stream does not affect distributed tracing.

Configure adaptive sampling in the Application Insights SDK.

Why wrong: Sampling does not enable tracing correlation.

Enable Application Map in the Azure portal for each service.

Why wrong: Application Map is a result of tracing, not a configuration.

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.

Use the 'docker login' command in the pipeline.

Why wrong: docker login is for authentication to a container registry, not for Azure resources.

Add a service principal connection to the pipeline.

Why wrong: Service principal connection is for non-managed identity authentication; managed identity avoids storing credentials.

Use the Azure CLI task with '–identity' flag.

Why wrong: The Azure CLI task can use managed identity, but the configuration requires the identity to be assigned and the task to run inside the container.

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'.

Comment requirements

Why wrong: Enforces commit message formats, not code quality.

Work item linking

Why wrong: Enforces linking to work items, not code quality.

Merge strategy

Why wrong: Controls how merges are performed, not quality.

Store all sensitive information in a variable group and reference it in the pipeline.

Why wrong: Variable groups do not automatically prevent logging; you must mark variables as secret.

Configure the service connection to use 'Read-only' scope.

Why wrong: Service connection scope does not affect log exposure.

Lead Time for Changes

Why wrong: This measures speed, not reliability.

CPU Usage

Why wrong: Not a DORA metric.

Deployment Frequency

Why wrong: This measures velocity, not reliability.

Azure App Configuration with Key Vault references

Why wrong: App Configuration is for application configuration, not pipeline secrets.

Storing secrets in a pipeline YAML file with encryption

Why wrong: YAML files are not encrypted and secrets would be visible in source control.

Removes the need for testing

Why wrong: Testing is still required for IaC templates.

Eliminates the need for documentation

Why wrong: IaC code serves as documentation but doesn't eliminate all documentation needs.

Lower infrastructure costs

Why wrong: IaC does not directly lower costs; it improves consistency and repeatability.

Use XML transformation tasks for web.config.

Why wrong: XML transformation is for config files, not a variable management strategy.

Use multi-stage YAML pipelines with stage-level variables.

Why wrong: This is a valid approach but the question asks for 'strategies' and the two most common are variable groups and Key Vault.