AZ-400 Question #106: Real Exam Question with Answer & Explanation

Question

Hotspot Question You currently use JIRA, Jenkins, and Octopus as part of your DevOps processes. You plan to use Azure DevOps to replace these tools. Which Azure DevOps service should you use to replace each tool? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Options

• __typehotspot
• variantdropdown

Explanation

Note: The dropdown answers show "None" in the data, but the correct answers are well-established. Here are the correct mappings with explanations.

Correct Mappings

1. JIRA → Boards

Why Boards is correct: JIRA is a project management and issue tracking tool — it manages backlogs, sprints, user stories, bugs, and work items. Azure Boards is the direct equivalent, providing Kanban boards, sprint planning, work item tracking, and backlog management.

Why the others are wrong:

• Build/Release pipelines — these are CI/CD tools, not project management.
• Repos — this is source control (like GitHub/Bitbucket), not issue tracking.

2. Jenkins → Build pipelines

Why Build pipelines is correct: Jenkins is a Continuous Integration (CI) tool — it compiles code, runs tests, and produces build artifacts when code is committed. Azure Build Pipelines (the CI half of Azure Pipelines) replicates this: trigger on commits, run build tasks, produce artifacts.

Why the others are wrong:

• Boards — project management, no build execution.
• Release pipelines — handles deployment of already-built artifacts, not the build itself.
• Repos — source control only.

3. Octopus → Release pipelines

Why Release pipelines is correct: Octopus Deploy is a Continuous Delivery (CD) / release management tool — it takes build artifacts and deploys them to environments (Dev → QA → Prod), managing approvals, gates, and rollback. Azure Release Pipelines is the CD equivalent, handling staged deployments with environment gates and approvals.

Why the others are wrong:

• Build pipelines — creates artifacts; Octopus/Release pipelines consume and deploy them.
• Boards — project tracking only.
• Repos — source control only.

Core Concept

The key distinction is the CI/CD split:

• CI (Continuous Integration) = build & test on commit → Jenkins → Build pipelines
• CD (Continuous Delivery) = deploy artifacts to environments → Octopus → Release pipelines
• Project tracking = manage work items/sprints → JIRA → Boards

No community discussion yet for this question.