ACP Atlassian Professional DevOps & CI/CD Integration 2 — Questions and Answers
Question 1: Which Atlassian on-premises CI/CD server product allows teams to define build plans with stages, jobs, and tasks for complex pipelines?
- Bamboo (Correct answer)
- Bitbucket Server
- Jira Automation
- Confluence Data Center
Correct answer: Bamboo
Bamboo is Atlassian's on-premises CI/CD server that organizes pipelines into plans, stages, jobs, and tasks, offering deep integration with Jira and Bitbucket.
Question 2: When a developer creates a pull request in Bitbucket, how does Jira Software typically reflect this activity?
- Jira automatically closes the linked issue
- The linked Jira issue displays the pull request status in the Development panel (Correct answer)
- Jira creates a new sprint with the branch name
- Bitbucket sends a Slack notification only
Correct answer: The linked Jira issue displays the pull request status in the Development panel
When a Bitbucket pull request is linked to a Jira issue via branch naming convention or Smart Commits, the Jira issue's Development panel shows the PR status (open, merged, declined).
Question 3: What does the concept of 'branch permissions' in Bitbucket enforce in a DevOps workflow?
- Limits which users can view repository branches
- Controls who can push, merge, or delete specific branches such as main or release (Correct answer)
- Automatically creates branches from Jira issues
- Restricts pipeline execution to administrators only
Correct answer: Controls who can push, merge, or delete specific branches such as main or release
Branch permissions in Bitbucket allow administrators to define which users or groups can write to, merge into, or delete protected branches, enforcing code review and quality gates.
Question 4: In an Atlassian DevOps workflow, which Jira feature helps teams track the status of all versions/releases of a software project, including linked issues and deployment status?
- Epics board
- Releases (formerly Versions) (Correct answer)
- Component management
- Workflow schemes
Correct answer: Releases (formerly Versions)
Jira's Releases feature (formerly called Versions) allows teams to group issues into releases, track their progress, and view deployment status from connected CI/CD pipelines.
Question 5: Which Atlassian Marketplace integration approach allows Jenkins pipelines to post build and deployment results back to Jira Software?
- Jira REST API polling by Jenkins
- The Atlassian Jira Software Cloud plugin for Jenkins (Correct answer)
- Manual webhook configuration only
- Bamboo relay service
Correct answer: The Atlassian Jira Software Cloud plugin for Jenkins
The official Atlassian Jira Software Cloud plugin for Jenkins enables Jenkins pipelines to send build and deployment events to Jira, populating the Deployments and Builds panels.
Question 6: In Bitbucket Pipelines, what is the purpose of 'pipe' steps?
- To pipe stdout from one step to the next step's stdin
- To execute pre-packaged, reusable automation tasks such as deploying to AWS or sending Slack notifications (Correct answer)
- To define parallel pipeline branches
- To cache dependencies between pipeline runs
Correct answer: To execute pre-packaged, reusable automation tasks such as deploying to AWS or sending Slack notifications
Bitbucket Pipes are Docker-based, pre-built integrations maintained by Atlassian and partners that wrap common DevOps tasks (e.g., AWS S3 deploy, Slack notify) into single-line pipe references.
Question 7: What is a key benefit of using Jira's 'Code' and 'Deployment' insights in the issue view for a DevOps team?
- It replaces the need for a separate sprint board
- It provides traceability from a feature request to the specific commit and deployment that delivered it (Correct answer)
- It automatically rolls back failed deployments
- It generates release notes from commit messages
Correct answer: It provides traceability from a feature request to the specific commit and deployment that delivered it
Jira's Code and Deployment insights link business requirements (issues) to technical artifacts (branches, commits, PRs, builds, deployments), giving full traceability across the delivery lifecycle.
Which Atlassian on-premises CI/CD server product allows teams to define build plans with stages, jobs, and tasks for complex pipelines?