A team integrates changes frequently and runs automated checks on each submission. This can help uncover conflicts and defects while the changes are still small.
9 Software Delivery and Project Practices Online Quiz Questions
Use this free practice quiz with 20 questions to review 9 Software Delivery and Project Practices, test your knowledge, and prepare for your next test or exam.
A team wants to reduce differences between what it tested and what it deploys. Which release practice best supports that goal?
- A
Build a new artifact for each environment so each can be tailored separately.
- B
Promote the same tested artifact through environments and provide environment-specific configuration separately.
- C
Deploy different artifacts to each environment and compare their test results after release.
- D
Skip testing in earlier environments and build the artifact only for production.
When assessing a project risk, a team considers its potential impact and its so it can prioritize attention.
What lightweight project document can record each risk, its impact, an owner, a planned response, and a review date?
A team has assessed a project risk and is planning how to respond. Which of the following are response options described in the risk management cycle? Select all that apply.
- A
Reduce its likelihood or impact.
- B
Ignore it without documenting or monitoring it.
- C
Prepare a contingency.
- D
Change the plan to avoid it.
- E
Knowingly accept it.
Software maintenance begins when software is in use; it is not simply a final phase after development.
- A
True
- B
False
A team is writing a work item so contributors can understand what successful completion means. What should the item clearly state?
- A
A list of every task the team might perform, without stating a goal.
- B
A status update that reports activity but does not define a result.
- C
The intended outcome and how the team will recognize completion.
- D
A fixed delivery date that replaces discussion of dependencies.
For a higher-risk change, a team releases first to a small share of users to look for problems before wider exposure. This staged rollout is called a .
What project coordination tool helps a team organize and prioritize upcoming work?
A team wants to identify evidence that could guide continuous improvement. Which inputs are described as useful? Select all that apply.
- A
User feedback.
- B
Test failures.
- C
The number of status meetings, considered alone.
- D
Operational incidents.
- E
Recurring delays.
After a production incident, a team wants to learn without assigning blame. Describe what a blameless review should examine and how the team should manage and evaluate the resulting actions.
A team has deployed a release and wants to limit harm if it behaves unexpectedly. Which action best fits sound release practices?
- A
Assume the deployment succeeded if the automated build passed.
- B
Check service health after deployment and have a tested way to roll back or otherwise mitigate a bad release.
- C
Wait for users to report problems before checking the service.
- D
Deploy a larger bundle of changes so any recovery applies to all of them at once.
Two teams discover that one component cannot be completed until another team delivers a dependency. What coordination practice best helps the teams manage the effect on sequencing and delivery dates?
- A
Keep dependencies private until all work is complete to avoid changing plans.
- B
Discuss dependencies only after a delivery date has been missed.
- C
Surface dependencies early because they can affect sequencing and delivery dates.
- D
Treat dependencies as status-reporting details that do not affect coordination.
A small pull request changes a payment service, and the CI pipeline reports a failed test. What is the most appropriate next step?
- A
Merge the change first, then wait for user reports to reveal defects.
- B
Investigate the failed test before merging, while the change is still small.
- C
Disable the failing test so the pull request can be merged.
- D
Deploy the change directly to production to test it with all users.
Which practice best helps make software releases repeatable and allows teams to check service health after deployment?
- A
Automate deployment and basic post-deployment checks where practical.
- B
Make each deployment depend on a different manual procedure.
- C
Keep deployment scripts out of version control so they can be changed informally.
- D
Skip health checks after deployment to avoid delaying a release.
Software maintenance work should be planned alongside new features.
- A
True
- B
False
Which coordination practice helps teams account for factors that may affect work sequencing and delivery dates?
- A
Wait until the final release review to mention dependencies.
- B
Identify dependencies between teams or components early.
- C
Treat dependencies as irrelevant to work sequencing.
- D
Record dependencies only after they have delayed delivery.
Which sequence best describes the ongoing risk-management cycle?
- A
Assess, monitor and revise, identify, then plan a response.
- B
Plan a response, accept every risk, identify, then stop monitoring.
- C
Identify, assess, plan a response, then monitor and revise.
- D
Monitor only after an incident, then identify and assess risks.
What is the name of the practice that aims to keep software changes releasable on demand?
What practice automates software deployment to help make releases repeatable and lower-risk?