A team's policy runs a build after each branch push, then tests. Merging requires both checks to pass and reviewer approval. What is the relative order of push, build, tests and an allowed merge?

• Push, tests, build, merge
• Push, build, merge, tests
• Push, build, tests, merge

A CI configuration enables a build job and automated tests on branch pushes. What does a triggered run check?

• Successful deployment to the production server
• Project preparation and the tested behaviour
• The branch's merge-conflict status

Passing a pipeline's configured checks automatically satisfies every completion and release requirement.

Checks start automatically after each push but report their final result only after 45 minutes. Which cost follows directly?

• A forty-five-minute pause between pushes
• A forty-five-minute wait for the final result
• A forty-five-minute loss of checks for changes pushed during the run

CI runs the expected setup, but code reads an untracked file present only on your laptop. What does the failure reveal?

• A dependency missing from the reproducible project setup
• A runner-permission problem with the file
• An assertion using an outdated expected file

A team's policy blocks merging while a required check fails. What is an appropriate next action?

• Accept the local pass and mark this check nonblocking
• Rerun the job until it passes, then merge without diagnosis
• Investigate the failure and restore a trustworthy required check

A developer dismisses a CI failure because the code passes locally. Which response is justified?

• Repair the runner to match the local setup
• Investigate the differing results without assuming the cause
• Revise the code to match the failing CI result

Both teams start checks on every push. A gets its final result after 7 minutes; B after 80. Which conclusion is justified?

• B waits longer for results; batching is a possible response
• B has less coverage because its checks take longer to finish
• B pushes less often to match the result schedule