You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- content: "The marketing team has asked you to add a banner to your company's website. They have two versions of this banner. They want to know which version produces more clickthroughs. Which deployment pattern might you use to help the marketing team identify the better version?"
19
-
choices:
20
-
- content: "Blue-green deployment"
21
-
isCorrect: false
22
-
explanation: "A blue-green deployment is better suited to helping you reduce downtime."
23
-
- content: "A/B testing"
24
-
isCorrect: true
25
-
explanation: "With A/B testing, you could randomly show both versions of the website to users. Then the marketing team can use statistical analysis to decide which version performs better."
26
-
- content: "Feature toggles"
27
-
isCorrect: false
28
-
explanation: "Feature toggles are better suited to exposing new features to a small, select number of users to see how they react."
29
-
- content: "You have a new feature for your website, and you're ready to deploy it. However, this feature is risky because it changes the way your users interact with the site. Which deployment patterns might you use to release to a small group of early adopters who have signed up to see new features?"
30
-
choices:
31
-
- content: "Canary release or progressive-exposure deployment"
32
-
isCorrect: true
33
-
explanation: "Both of these deployment patterns expose a new feature to only a small subset of users. After you validate the feature with this smaller subset, you can then progressively roll out to a larger set of users."
34
-
- content: "A/B testing or a dark launch"
35
-
isCorrect: false
36
-
explanation: "A/B testing is typically used to sample users at random. In a dark launch, test users typically don't know that they're testing new features."
37
-
- content: "Blue-green deployment or feature toggles"
38
-
isCorrect: false
39
-
explanation: "Although you might use a feature toggle to expose your feature to select users, a blue-green deployment is meant to help you reduce downtime."
40
-
- content: "You're not sure how your users will react to your new feature. You want to release your feature to a small, random sample of users to see how they react. Which deployment pattern might you use?"
41
-
choices:
42
-
- content: "Blue-green deployment"
43
-
isCorrect: false
44
-
explanation: "A blue-green deployment is better suited to helping you reduce downtime."
45
-
- content: "Dark launch"
46
-
isCorrect: true
47
-
explanation: "Because you want a random sample, a dark launch can help you gradually release your feature while you collect feedback and test performance."
48
-
- content: "A/B testing"
49
-
isCorrect: false
50
-
explanation: "Although A/B testing is typically used to sample users at random, it's more commonly used to test two or more variations of a feature against each other."
- content: "The marketing team has asked you to add a banner to your company's website. They have two versions of this banner. They want to know which version produces more clickthroughs. Which deployment pattern might you use to help the marketing team identify the better version?"
19
+
choices:
20
+
- content: "Blue-green deployment"
21
+
isCorrect: false
22
+
explanation: "A blue-green deployment is better suited to helping you reduce downtime."
23
+
- content: "A/B testing"
24
+
isCorrect: true
25
+
explanation: "With A/B testing, you could randomly show both versions of the website to users. Then the marketing team can use statistical analysis to decide which version performs better."
26
+
- content: "Feature toggles"
27
+
isCorrect: false
28
+
explanation: "Feature toggles are better suited to exposing new features to a small and select number of users to see how they react."
29
+
- content: "You have a new feature for your website, and you're ready to deploy it. However, this feature is risky because it changes the way your users interact with the site. Which deployment patterns might you use to release to a small group of early adopters who have signed up to see new features?"
30
+
choices:
31
+
- content: "Canary release or progressive-exposure deployment"
32
+
isCorrect: true
33
+
explanation: "Both of these deployment patterns expose a new feature to only a small subset of users. After you validate the feature with this smaller subset, you can then progressively roll out to a larger set of users."
34
+
- content: "A/B testing or a dark launch"
35
+
isCorrect: false
36
+
explanation: "A/B testing is typically used to sample users at random. In a dark launch, test users typically don't know that they're testing new features."
37
+
- content: "Blue-green deployment or feature toggles"
38
+
isCorrect: false
39
+
explanation: "Although you might use a feature toggle to expose your feature to select users, a blue-green deployment is meant to help you reduce downtime."
40
+
- content: "You're not sure how your users will react to your new feature. You want to release your feature to a small, random sample of users to see how they react. Which deployment pattern might you use?"
41
+
choices:
42
+
- content: "Blue-green deployment"
43
+
isCorrect: false
44
+
explanation: "A blue-green deployment is better suited to helping you reduce downtime."
45
+
- content: "Dark launch"
46
+
isCorrect: true
47
+
explanation: "Because you want a random sample, a dark launch can help you gradually release your feature while you collect feedback and test performance."
48
+
- content: "A/B testing"
49
+
isCorrect: false
50
+
explanation: "Although A/B testing is typically used to sample users at random, it's more commonly used to test two or more variations of a feature against each other."
Copy file name to clipboardExpand all lines: learn-pr/azure-devops/manage-release-cadence/includes/1-introduction.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
In this learning path, you've been helping the Tailspin Toys team set up an automated release pipeline. The pipeline includes multiple stages, and both functional and nonfunctional tests.
2
2
3
-
In this module, you help the team solve another problem, which is how to implement a deployment pattern to release to production in a way that's best for the company and their users. You'll help them evaluate the possibilities and then implement the one they choose.
3
+
In this module, you help the team solve another problem, which is how to implement a deployment pattern to release to production in a way that's best for the company and their users. You'll help them evaluate the possibilities, and then implement the one they choose.
4
4
5
5
## Learning objectives
6
6
@@ -16,18 +16,18 @@ The modules in this learning path are part of a progression.
16
16
17
17
To follow the progression from the beginning, be sure to first complete these learning paths:
18
18
19
-
*[Get started with Azure DevOps](../../../paths/evolve-your-devops-practices/index.yml?azure-portal=true)
20
-
*[Build applications with Azure DevOps](../../../paths/build-applications-with-azure-devops/index.yml?azure-portal=true)
19
+
-[Get started with Azure DevOps](../../../paths/evolve-your-devops-practices/index.yml?azure-portal=true)
20
+
-[Build applications with Azure DevOps](../../../paths/build-applications-with-azure-devops/index.yml?azure-portal=true)
21
21
22
22
We also recommend that you start at the beginning of this learning path, [Deploy applications with Azure DevOps](../../../paths/deploy-applications-with-azure-devops/index.yml?azure-portal=true).
23
23
24
24
If you want to go through just this module, then you need to set up a development environment on your Windows, macOS, or Linux system. You'll need the following resources:
25
25
26
-
- An [Azure DevOps organization](/azure/devops/pipelines/get-started/pipelines-sign-up) with access to [parallel jobs](/azure/devops/pipelines/licensing/concurrent-jobs). If your organization does not have access to parallel jobs, you can request parallel jobs for free for public or private projects using [this form](https://aka.ms/azpipelines-parallelism-request). Your request will take 2-3 business days.
26
+
- An [Azure DevOps organization](/azure/devops/pipelines/get-started/pipelines-sign-up) with access to [parallel jobs](/azure/devops/pipelines/licensing/concurrent-jobs). If your organization doesn't have access to parallel jobs, you can request parallel jobs for free for public or private projects using [this form](https://aka.ms/azpipelines-parallelism-request). Your request will take 2-3 business days.
27
27
- An [Azure subscription](https://azure.microsoft.com/free/?azure-portal=true)
28
28
- A [GitHub](https://github.com/join?azure-portal=true) account
29
29
-[Visual Studio Code](https://code.visualstudio.com?azure-portal=true)
You can get started with Azure and Azure DevOps for free. You don't need an Azure subscription to work with Azure DevOps, but here you'll use Azure DevOps to deploy to resources that exist in your Azure subscription.
0 commit comments