Get the Preplance app for a seamless learning experience. Practice offline, get daily streaks, and stay ahead with real-time interview updates.
Get it on
Google Play
4.9/5 Rating on Store
Accenture · CI/CD Pipelines
Practice CI/CD Pipelines questions specifically asked in Accenture interviews – ideal for online test preparation, technical rounds and final HR discussions.
Questions
9
Tagged for this company + subject
Company
Accenture
View company-wise questions
Subject
CI/CD Pipelines
Explore topic-wise practice
Go through each question and its explanation. Use this page for targeted revision just before your Accenture CI/CD Pipelines round.
Treat pull requests like a secure door. Only green checks and an approval let code in. This prevents broken changes from landing on the main branch.
For complete preparation, combine this company + subject page with full company-wise practice and subject-wise practice. You can also explore other companies and topics from the links below.
Never hard code secrets in scripts or in the repo. Store them in a secret manager or the CI vault and inject at runtime only. Scope access with least privilege and rotate keys regularly to reduce blast radius.
env:
DB_PASSWORD: ${{ secrets.DB_PASSWORD }}CI is about integrating code often and proving it works with fast checks. CD makes sure every successful change can be deployed at any time with a push of a button.
Stages model the flow. Jobs inside a stage can fan out in parallel, then the next stage runs only when the current one is green. This cuts time and keeps the pipeline easy to read.
stages: [build, test, deploy]
jobs:
build: {}
test_unit: {}
test_int: {}Store secrets in the CI vault or a secret manager. Inject at runtime as environment variables or mounted files. Never commit them to the repo. Scope access with least privilege, mask logs, and rotate keys on a schedule or on exposure.
Declarative gives you a clear, opinionated structure that teams can read quickly. Scripted lets you program every detail with Groovy, at the cost of complexity. Pick based on team skill and need for control.
pipeline {
stages { stage('Build'){ steps{ sh 'mvn -B package' } } }
}Quarantine known flaky tests so they do not gate merges, but still report them loudly. Add limited retries and gather evidence. Fix root causes like timing, shared state, or network calls, then return the test to the blocking lane once stable.
You run blue and green side by side. Deploy to the idle one, test, then flip traffic. Rollback is simple because the old version is still available.
Build once, promote the same artifact forward. Run integration tests in staging, then require an approval or automated checks before prod. Keep environment config externalized so the artifact stays identical across stages.
artifact: app-1.4.2.tgz promote: dev -> staging -> prod