A Jenkins pipeline has a stage that runs integration tests. The team wants to skip this stage if the build was triggered by a pull request, but run it for all other triggers. Which approach should they use?

Use a `parallel` block to run the stage only if a parameter is set

Use a `when` directive with `expression` checking `env.BRANCH_NAME` or `params` to detect the trigger

Use a `post` block to conditionally run the stage

Use a `tools` directive to conditionally skip the stage

In GitHub Actions, where is the CI tool configuration defined for a repository?

In the azure-pipelines.yml file

In the .github/workflows directory as YAML files

In the Jenkinsfile at the repository root

A Jenkins pipeline uses a shared library for common build steps. The team wants to update the library version used by the pipeline without modifying the Jenkinsfile. Which approach should they use?

Use a `library` step in the pipeline to load a specific version

Edit the Jenkinsfile to change the library version

Use a folder-level shared library and update the version in the folder configuration

Use a global shared library with a version parameter and reference it in the Jenkinsfile

A team wants to define a CI pipeline as code so that it is versioned and reviewed like application code. They use both Jenkins and GitHub Actions. Which approach should they take?

Use a Jenkinsfile in the repository and a GitHub Actions workflow YAML file in the `.github/workflows` directory

Use a single YAML file that both Jenkins and GitHub Actions can interpret

Configure both tools using their web UI and document the steps in a wiki

Store the pipeline definitions in a shared network drive and reference them from both tools

A GitHub Actions workflow has a job that runs on `ubuntu-latest`. The team wants to ensure the job runs only if the previous job in the workflow succeeded, and they also want to pass a value from the previous job to this job. Which configuration should they use?

Use `needs` on the job and `outputs` from the previous job

Use `on: workflow_run` to trigger the job

Use `if: always()` on the job and `env` variables

Use `runs-on` with a matrix and `strategy`

CompTIAAutoOps+

Domain 3Objective 3

Analyze Configurations to Manage Basic Automation Pipelines AT0-001 Practice Questions (Page 4)

Part of the Continuous Integration domain, which accounts for 24% of the AT0-001 exam. CompTIA does not publish an official question count, but from its 60-minute exam (~25–40 total, ~6–10 in this domain), expect 2–3 from this objective — we provide 25 practice questions to prepare you well beyond it. (estimate)

25questions here

5free pages

6concepts

24%of the exam

Questions 16–20

16application · medium
A Jenkins pipeline has a stage that runs integration tests. The team wants to skip this stage if the build was triggered by a pull request, but run it for all other triggers. Which approach should they use?
Select an answer first
17foundation · easy
In GitHub Actions, where is the CI tool configuration defined for a repository?
Select an answer first
18expert · hard
A Jenkins pipeline uses a shared library for common build steps. The team wants to update the library version used by the pipeline without modifying the Jenkinsfile. Which approach should they use?
Select an answer first
19application · medium
A team wants to define a CI pipeline as code so that it is versioned and reviewed like application code. They use both Jenkins and GitHub Actions. Which approach should they take?
Select an answer first
20expert · hard
A GitHub Actions workflow has a job that runs on `ubuntu-latest`. The team wants to ensure the job runs only if the previous job in the workflow succeeded, and they also want to pass a value from the previous job to this job. Which configuration should they use?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AT0-001

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by CompTIA. “AT0-001” is a trademark of its owner, used for identification only.