HOTSPOT -
You are configuring a release pipeline in Azure DevOps as shown in the exhibit.
Use the drop-down menus to select the answer choice that answers each question based on the information presented in the graphic.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: 5 -
There are five stages: Development, QA, Pre-production, Load Test and Production. They all have triggers.
Box 2: The Internal Review stage
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/triggers
correct answer is 7 and web application artifact
And what will you change in the web application artifact? The trigger is already ON
However, it could be that Continuous deployment is not set, but instead is the Pull Request trigger (that also adds a tick to the flag), and maybe that's not considered "Continuous delivery"
Yes you are right in the trigger of artifact we have 'Pull request trigger' and 'Continuous deployment trigger' enabling any of this 2 give a check mark on the bolt icon of artifact
absolutely yes
The artifact had set for auto-trigger already. the internal review doesn't set artifact for CD answer: 7 & internal review
I think you are right. The only component where you can enable Continuous Deployment is the artifact. The mark you can see on the Web Application artifact in my opinion is for Pull Request trigger. In fact we have an internal review stage. So for me correct answer are 7 and web application artifact
For continuous delivery all stages should be in chains. Internal review stage must be modified to form a chain. As per me, it is 7 and internal review stage
I think this is a good explanation for Continuous delivery
7 Internal Review stage
In fact, in Internal Review stage, there is nowhere to enable continious delivery.... no button to do it... If you check web application artifact's UI, there is a button to enable it....
Exactly, I've checked it you can turn in on Artifact itself no stages
For me it : - 7 - Production stage
It will be 6 and Production as it ask for delivery. Delivery is manual review before deploying code to Prod
Selected during exam. 6 The Web Application artifact
Correct answer is 7 and development state. Trigger set: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/triggers?view=azure-devops https://azure.microsoft.com/en-us/overview/continuous-delivery-vs-continuous-deployment/
My bad Box 1: 5 stages and Box 2: Development stage.
7 Web Application artifact
you´re right Eltooth. 7 Web Application artifact https://learn.microsoft.com/en-us/azure/devops/pipelines/release/triggers?view=azure-devops
Based on this link [link: https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment], which states in the 'Overview': "Continuous delivery follows the testing that happens during continuous integration and pushes changes to a staging or production system." Wouldn't the answer be DEVELOPMENT STAGE, as it would be the stage just before testing begins?
Exactly, I would also go with "development stage". That is why there is an approval after the development stage. Regarding the triggers, it is asked "how many stages...", which means the artifacts should not be counted. I just checked in a pipeline, the "internal review" stage as it is in the image it has a "Manual only" trigger, there should be no checked mark next to the lightning bolt. My answer is: 6 stages.
Final answer after going through all the comments 7 Internal Review stage
7 web application artifact
7 and Production Stage
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/triggers?view=azure-devops#continuous-deployment-triggers Artifact to set the trigger for Continuous Delivery 7 lightning bolts ticked so 7 stages
I will answer with 7 and internal review, may there is a gate condition in Development stage
correct answer is 7 and web application artifact https://learn.microsoft.com/en-us/azure/devops/pipelines/release/triggers?view=azure-devops
From my experience, there are 6 stages with triggers set because the "Internal Review" stage does not have trigger enabled, requiring manual execution. To enable Continuous Delivery, it must be configured in the "Web Application artifact"
7 and Internal Review
The trigger in the artifacts is called "continuous deployment" (not delivery), so unless the question is worded incorrectly here, the answer should be 7 and the Internal Review Stage. If it indeed is intended to be "continuous delivery" this description helps clarify why we need to get that review stage into the overall process: Where Continuous Deployment focuses on the actual deployment, Continuous Delivery focuses on the release and release strategy. An elusive goal would be a “push of a button” to get changes into production. That “push of a button” is Continuous Delivery. https://www.harness.io/blog/continuous-delivery-vs-continuous-deployment