Free Practice Quiz Question List

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.

20 questions
01
True or false
1 point

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.

  1. A

    True

  2. B

    False

02
Choose one
1 point

A team wants to reduce differences between what it tested and what it deploys. Which release practice best supports that goal?

  1. A

    Build a new artifact for each environment so each can be tailored separately.

  2. B

    Promote the same tested artifact through environments and provide environment-specific configuration separately.

  3. C

    Deploy different artifacts to each environment and compare their test results after release.

  4. D

    Skip testing in earlier environments and build the artifact only for production.

03
Fill in the blank
1 point

When assessing a project risk, a team considers its potential impact and its so it can prioritize attention.

04
Written response
1 point

What lightweight project document can record each risk, its impact, an owner, a planned response, and a review date?

05
Choose all
1 point

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.

  1. A

    Reduce its likelihood or impact.

  2. B

    Ignore it without documenting or monitoring it.

  3. C

    Prepare a contingency.

  4. D

    Change the plan to avoid it.

  5. E

    Knowingly accept it.

06
True or false
1 point

Software maintenance begins when software is in use; it is not simply a final phase after development.

  1. A

    True

  2. B

    False

07
Choose one
1 point

A team is writing a work item so contributors can understand what successful completion means. What should the item clearly state?

  1. A

    A list of every task the team might perform, without stating a goal.

  2. B

    A status update that reports activity but does not define a result.

  3. C

    The intended outcome and how the team will recognize completion.

  4. D

    A fixed delivery date that replaces discussion of dependencies.

08
Fill in the blank
1 point

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 .

09
Written response
1 point

What project coordination tool helps a team organize and prioritize upcoming work?

10
Choose all
1 point

A team wants to identify evidence that could guide continuous improvement. Which inputs are described as useful? Select all that apply.

  1. A

    User feedback.

  2. B

    Test failures.

  3. C

    The number of status meetings, considered alone.

  4. D

    Operational incidents.

  5. E

    Recurring delays.

11
Open ended
1 point

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.

12
Choose one
1 point

A team has deployed a release and wants to limit harm if it behaves unexpectedly. Which action best fits sound release practices?

  1. A

    Assume the deployment succeeded if the automated build passed.

  2. B

    Check service health after deployment and have a tested way to roll back or otherwise mitigate a bad release.

  3. C

    Wait for users to report problems before checking the service.

  4. D

    Deploy a larger bundle of changes so any recovery applies to all of them at once.

13
Choose one
1 point

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?

  1. A

    Keep dependencies private until all work is complete to avoid changing plans.

  2. B

    Discuss dependencies only after a delivery date has been missed.

  3. C

    Surface dependencies early because they can affect sequencing and delivery dates.

  4. D

    Treat dependencies as status-reporting details that do not affect coordination.

14
Choose one
1 point

A small pull request changes a payment service, and the CI pipeline reports a failed test. What is the most appropriate next step?

  1. A

    Merge the change first, then wait for user reports to reveal defects.

  2. B

    Investigate the failed test before merging, while the change is still small.

  3. C

    Disable the failing test so the pull request can be merged.

  4. D

    Deploy the change directly to production to test it with all users.

15
Choose one
1 point

Which practice best helps make software releases repeatable and allows teams to check service health after deployment?

  1. A

    Automate deployment and basic post-deployment checks where practical.

  2. B

    Make each deployment depend on a different manual procedure.

  3. C

    Keep deployment scripts out of version control so they can be changed informally.

  4. D

    Skip health checks after deployment to avoid delaying a release.

16
True or false
1 point

Software maintenance work should be planned alongside new features.

  1. A

    True

  2. B

    False

17
Choose one
1 point

Which coordination practice helps teams account for factors that may affect work sequencing and delivery dates?

  1. A

    Wait until the final release review to mention dependencies.

  2. B

    Identify dependencies between teams or components early.

  3. C

    Treat dependencies as irrelevant to work sequencing.

  4. D

    Record dependencies only after they have delayed delivery.

18
Choose one
1 point

Which sequence best describes the ongoing risk-management cycle?

  1. A

    Assess, monitor and revise, identify, then plan a response.

  2. B

    Plan a response, accept every risk, identify, then stop monitoring.

  3. C

    Identify, assess, plan a response, then monitor and revise.

  4. D

    Monitor only after an incident, then identify and assess risks.

19
Written response
1 point

What is the name of the practice that aims to keep software changes releasable on demand?

20
Written response
1 point

What practice automates software deployment to help make releases repeatable and lower-risk?