QuestionQ33

Risk Identification and Mitigation

Universal Containers (UC) is evaluating a minor-change policy for a set of low-risk user stories that UC administrators receive frequently. The policy would permit administrators to make these changes directly in production. UC does not have continuous integration/continuous delivery (CI/CD) in place.

Which three best practices should the architect recommend for UC’s new change policy?

Choose three
  • A Minor changes do not need to be documented and can be made at any time
  • B All changes should still be tested
  • C CI/CD is required in to successfully manage minor changes
  • D Downstream environments will not be automatically updated when production changes
  • E Minor changes should be thoroughly documented and follow some type of standard cadence
Explanation

Even low-risk production changes require testing because an untested update can disrupt processes, data, or users. Production changes also do not automatically synchronize to downstream sandbox environments; those environments require an explicit refresh or deployment/update process. A controlled policy should document minor changes and use a standard cadence to preserve traceability, governance, and predictable releases. CI/CD can reduce manual-release risk but is not required to manage such changes.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!