The release and deployment lifecycle involves several key stages. 'Release build and test' is a fundamental phase where the new or changed service components are assembled into a release package and subjected to rigorous testing to ensure they meet requirements and are fit for purpose. Following the deployment, the 'Review and close' phase is crucial for evaluating the success of the release, capturing lessons learned for future improvements, and formally closing the release and associated change records. These two activities represent core parts of the beginning and end of the release and deployment workflow.

'Categorize and record' is an initial activity of the incident management practice, used for logging and classifying new incidents, not for managing releases.

'Change authorization and schedule' is a distinct activity performed within the change enablement practice, which typically occurs before the release and deployment activities begin.

AXELOS. (2019). ITIL® Foundation

ITIL 4 Edition. TSO (The Stationery Office).

Section 5.2.14 (Release management): This section describes release management's purpose as making new and changed services available

which involves planning

scheduling

and controlling the build

test

and deployment of releases. This supports the 'Release build and test' phase.

Section 5.2.6 (Deployment management): This section details the practice of moving components to live environments. The activities implicitly include building the deployment package and testing it before and after the move. The post-deployment review is a key part of ensuring a successful deployment

aligning with 'Review and close'.

Section 5.2.8 (Incident management): This section explicitly states that incident management includes the recording and categorization of incidents

making option 3 incorrect in the context of release and deployment.

Section 5.2.4 (Change enablement): This section describes the authorization and scheduling of changes as a core activity of this practice

confirming that option 4 belongs to change enablement

not release and deployment.