Well, this is basically an approach that can be considered to AVOID situation when the deployment process needs to be made more secure. Many times there is a NEED to deploy resources for one module of the deployment and not to the other. For example, users are deployed for testing are not allowed to TAKE part in any activity related to the production. In such a scenario, this approach ensure that all the PROCESSES related to deployment remain consistent when the users deployed for testing try to take part in production. Such situation is considered as consistent releases because the process REMAINS consistent.

Well, this is basically an approach that can be considered to avoid situation when the deployment process needs to be made more secure. Many times there is a need to deploy resources for one module of the deployment and not to the other. For example, users are deployed for testing are not allowed to take part in any activity related to the production. In such a scenario, this approach ensure that all the processes related to deployment remain consistent when the users deployed for testing try to take part in production. Such situation is considered as consistent releases because the process remains consistent.