You are reviewing your deployment pipeline in Google Cloud Deploy. You must reduce toil in the pipeline, and you want to minimize the amount of time it takes to complete an end-to-end deployment. What should you do? (Choose two.)
You are reviewing your deployment pipeline in Google Cloud Deploy. You must reduce toil in the pipeline, and you want to minimize the amount of time it takes to complete an end-to-end deployment. What should you do? (Choose two.)
To reduce toil and minimize the time it takes to complete an end-to-end deployment, you should divide the automation steps into smaller tasks and automate promotion approvals from the development environment to the test environment. Dividing automation steps into smaller tasks allows for better management and potentially parallel execution, which can speed up the deployment process. Automating promotion approvals eliminates the need for manual intervention, thus streamlining workflow and reducing delays.
Chose A, E
imho: A. Create a trigger to notify the required team to complete the next step when manual intervention is required. We want to reduce the time for end-to-end deployment. Notification of required manual intervention can reduce this time. B. Divide the automation steps into smaller tasks. This doesn't reduce toil or time, but maybe I miss something here? C. Use a script to automate the creation of the deployment pipeline in Google Cloud Deploy. We would rather use a webhook to create a deployment or pub/sub message. Doesn't sound like an answer to this question. D. Add more engineers to finish the manual steps. This simply doesn't work here. E. Automate promotion approvals from the development environment to the test environment. This reduces toil if covered by appropriate tests.
Chose based on eliminating other options
The recommended approaches to reduce toil and minimize deployment time in Google Cloud Deploy are (options B and E). - Option B, dividing automation steps into smaller tasks, allows for better manageability and flexibility in the deployment process. This enables parallel execution of smaller tasks, speeding up the overall deployment. - Option E, automating promotion approvals, eliminates manual intervention and streamlines the progression from development to test environments, further reducing delays and potential errors associated with manual approval processes. Both options contribute to a more efficient and automated deployment pipeline in Google Cloud Deploy.
Vote BE
Should be BE https://sre.google/workbook/eliminating-toil/
It is BE
main purpose of toil is to reduce the CICD build, deploy time. Not to break the work in pieces. B is not toil, it is good to troubleshoot the code or cicd configuration
To reduce toil and minimize deployment time, the key is to reduce manual steps and optimize automation. A. Create a trigger to notify the required team: - If manual intervention is required, a trigger-based notification ensures that teams act quickly, reducing wait times and bottlenecks. - This improves efficiency by minimizing delays caused by human response times. E. Automate promotion approvals: - Manual approvals for every environment slow down deployments. - Automating promotions from development to test ensures a smoother and faster pipeline while still allowing manual approvals for later, more critical stages (e.g., production).
Why Not the Others? B. Dividing automation into smaller tasks does not necessarily speed up the pipeline. It might even introduce additional complexity. C. Using a script to automate pipeline creation helps initial setup, but it does not reduce deployment time in an existing pipeline. D. Adding more engineers to manual steps increases human dependency, which contradicts the goal of reducing toil.