A lead cloud infrastructure administrator is preparing to deploy an automated identity provider (IdP) federation update that affects single sign-on (SSO) access for all global corporate users. The administrator has fully documented the business justification, established the scope of the change, conducted a formal risk assessment, detailed the implementation steps, and validated a comprehensive rollback plan. Which of the following actions must the administrator take NEXT to adhere to standard change management procedures prior to seeking Change Advisory Board (CAB) authorization?
- Draft and schedule an end-user notification detailing the scheduled maintenance window, potential service disruptions, and support contact details.Answer
- BApply the federation configuration changes to a subset of production servers during off-peak hours to gather preliminary deployment metrics.
- CExecute the rollback plan in the primary datacenter to verify that current identity services can automatically fail over if issues arise.
- DBypass the formal approval process and initiate deployment under emergency change protocols because the implementation steps are fully documented.
Answer
Draft and schedule an end-user notification detailing the scheduled maintenance window, potential service disruptions, and support contact details.
In enterprise IT environments, a complete change proposal submitted to the Change Advisory Board (CAB) must include all required documentation elements: purpose, scope, risk assessment, implementation plan, rollback plan, and the end-user notification schedule. Preparing the end-user notification prior to CAB review ensures that stakeholders are aware of upcoming maintenance windows and potential service downtime, allowing the board to evaluate both technical risk and operational impact.
Step-by-Step Solution
Key Concept
Change Management Processes & Documentation Requirements
Estimated Time:1m 30s