Scenario practice questions

A team is migrating from TFVC to Git. They have a large codebase with many branches. What is the recommended approach to preserve the history during migration?

Trap 1: Copy the latest version of the code to a new Git repository and…

Loses all history.

Trap 2: Use the Git-TF tool to clone the TFVC repository

Git-TF is deprecated; git-tfs is recommended.

Trap 3: Export TFVC as a Git bundle and import with --no-metadata

Bundles are for Git-to-Git, not TFVC.

A
Copy the latest version of the code to a new Git repository and start fresh
Why wrong: Loses all history.
B
Use the Git-TF tool to clone the TFVC repository
Why wrong: Git-TF is deprecated; git-tfs is recommended.
C
Use the git-tfs tool to clone the TFVC repository with changesets
git-tfs converts TFVC changesets into Git commits preserving history.
D
Export TFVC as a Git bundle and import with --no-metadata
Why wrong: Bundles are for Git-to-Git, not TFVC.

Question 2hardmultiple choice

You are troubleshooting an intermittent performance issue in a web application. Application Insights shows a high number of failed dependency calls to Azure SQL Database. The errors are SqlException with error code -2 (timeout). What is the most likely cause and recommended fix?

Trap 1: The SQL Server firewall is blocking the application IP; add a…

Firewall issues cause login failures, not timeouts.

Trap 2: The database is experiencing deadlocks; enable read committed…

Deadlocks cause error 1205, not timeout.

Trap 3: The database DTU limit is being exceeded; scale up the service tier.

DTU throttling causes different errors.

A
The application is exhausting the connection pool; increase Max Pool Size in the connection string.
Timeouts often indicate pool exhaustion.
B
The SQL Server firewall is blocking the application IP; add a firewall rule.
Why wrong: Firewall issues cause login failures, not timeouts.
C
The database is experiencing deadlocks; enable read committed snapshot isolation.
Why wrong: Deadlocks cause error 1205, not timeout.
D
The database DTU limit is being exceeded; scale up the service tier.
Why wrong: DTU throttling causes different errors.

Question 3mediummultiple choice

A company recently migrated its CI/CD pipelines from Jenkins to Azure Pipelines. The development team is experiencing frequent build failures due to conflicting changes when multiple developers push code simultaneously. The team wants to maintain a linear history and avoid merge commits. Which strategy should you recommend?

Trap 1: Switch to Git with a central repository and require merge commits.

This generates merge commits and does not prevent conflicts.

Trap 2: Enforce a rebase strategy for all pull requests in the branch…

Rebase does not prevent concurrent pushes; conflicts must still be resolved.

Trap 3: Configure Azure Repos to use squash merge when completing pull…

Squash merge still allows concurrent pushes and conflicts.

A
Switch to Git with a central repository and require merge commits.
Why wrong: This generates merge commits and does not prevent conflicts.
B
Enforce a rebase strategy for all pull requests in the branch policy.
Why wrong: Rebase does not prevent concurrent pushes; conflicts must still be resolved.
C
Use Team Foundation Version Control (TFVC) with exclusive checkout enabled.
TFVC with exclusive checkout locks files, preventing concurrent edits and ensuring linear history.
D
Configure Azure Repos to use squash merge when completing pull requests.
Why wrong: Squash merge still allows concurrent pushes and conflicts.

Question 4mediummultiple choice

Your team uses Azure Boards to manage work items. They want to automatically update the status of a work item to 'Resolved' when a pull request that contains the work item ID is merged. Which feature should you configure?

Trap 1: Instruct developers to manually update the work item after merging.

Manual updates are error-prone and not automated.

Trap 2: Set up a branch policy that requires linked work items.

Branch policies enforce linking but do not update status.

Trap 3: Create a service hook to call Azure DevOps REST API on pull request…

Service hooks require custom development; not the simplest solution.

A
Enable the 'Automatically update work item status' setting in the repository's pull request configuration.
This built-in feature updates work item status on merge.
B
Instruct developers to manually update the work item after merging.
Why wrong: Manual updates are error-prone and not automated.
C
Set up a branch policy that requires linked work items.
Why wrong: Branch policies enforce linking but do not update status.
D
Create a service hook to call Azure DevOps REST API on pull request merge.
Why wrong: Service hooks require custom development; not the simplest solution.

Question 5mediummultiple choice

Your team is migrating from TFVC to Git in Azure Repos. They want to preserve the history of all branches. Which migration tool should you use?

Trap 1: GitHub Importer

For importing to GitHub.

Trap 2: Azure DevOps Migration Tools

Migrates work items, not repo history.

Trap 3: git-svn

For Subversion, not TFVC.

A
GitHub Importer
Why wrong: For importing to GitHub.
B
Azure DevOps Migration Tools
Why wrong: Migrates work items, not repo history.
C
git-tfs tool
Preserves history and branches.
D
git-svn
Why wrong: For Subversion, not TFVC.

Question 6hardmultiple choice

You have a multi-stage YAML pipeline that builds and deploys a containerized application to Azure Kubernetes Service (AKS). The build stage runs successfully, but the deploy stage fails with an error: 'Error: failed to get credentials: context deadline exceeded'. You verify that the AKS cluster is running and that the service connection is valid. What is the most likely cause?

Trap 1: The Azure service connection has expired.

The scenario states the service connection is valid.

Trap 2: The service principal used by the pipeline does not have RBAC…

RBAC issues cause authorization errors, not timeouts.

Trap 3: The container registry is not accessible from the build agent.

Container registry access is unrelated to AKS API server connectivity.

A
The Azure service connection has expired.
Why wrong: The scenario states the service connection is valid.
B
The service principal used by the pipeline does not have RBAC permissions on the cluster.
Why wrong: RBAC issues cause authorization errors, not timeouts.
C
The container registry is not accessible from the build agent.
Why wrong: Container registry access is unrelated to AKS API server connectivity.
D
The build agent's IP address is not allowed by the AKS cluster's network policies.
Network restrictions can cause timeouts when trying to connect to the API server.

Question 7mediummultiple choice

You are designing a build pipeline for a Java application hosted in Azure Repos. The pipeline needs to run unit tests, package the application as a JAR file, and publish the build artifact. Which task should you use to publish the JAR file as a pipeline artifact?

Trap 1: Publish Build Artifacts task

Although this task publishes build artifacts, Publish Pipeline Artifact is the modern equivalent and the scenario uses a YAML pipeline where Publish Pipeline Artifact is recommended.

Trap 2: Copy Files task

Copy Files copies files to a staging directory but does not publish them as artifacts.

Trap 3: Archive Files task

Archive Files creates a ZIP archive but does not publish it as an artifact.

A
Publish Build Artifacts task
Why wrong: Although this task publishes build artifacts, Publish Pipeline Artifact is the modern equivalent and the scenario uses a YAML pipeline where Publish Pipeline Artifact is recommended.
B
Copy Files task
Why wrong: Copy Files copies files to a staging directory but does not publish them as artifacts.
C
Archive Files task
Why wrong: Archive Files creates a ZIP archive but does not publish it as an artifact.
D
Publish Pipeline Artifact task
Publish Pipeline Artifact publishes files as pipeline artifacts that can be used in subsequent stages.