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: What's the best way for the team to create a template that deploys to both test and production environments?
20
-
choices:
21
-
- content: Create a template that deploys all of the resources for the manufacturing application. Add template parameters for the values that might change between environments.
22
-
isCorrect: true
23
-
explanation: Correct. Template parameters are a great way to manage multiple environments. You can specify different values for the parameters when you deploy the template into the test and production environments.
24
-
- content: Create a module that deploys all of the resources for the manufacturing application. Create separate Bicep templates for each environment, and add the shared module to each environment's template.
25
-
isCorrect: false
26
-
explanation: Incorrect. Modules can be a great way to reuse your Bicep code, but when you're deploying multiple environments, there's usually a simpler way to keep track of the different configurations for each deployment.
27
-
- content: Create a template that deploys all of the resources required for the manufacturing application. Add variables for the values that might change between environments.
28
-
isCorrect: false
29
-
explanation: Incorrect. Variables have the same value, so you don't usually need to consider them when you deploy multiple environments.
30
-
- content: |
31
-
The template that the team has developed includes this line:<br />
- content: Whoever deploys the template must specify a value for the `siteName` parameter.
36
-
isCorrect: false
37
-
explanation: Incorrect. The `siteName` parameter has a _default value_ specified, which means that deployments don't have to specify the parameter value. If they don't, the parameter's default value is used.
38
-
- content: The `siteName` parameter will have a different default value every time the template is deployed.
39
-
isCorrect: false
40
-
explanation: Incorrect. The parameter's default value is set through the `uniqueString()` function, which has been seeded with the resource group's ID. Therefore, the value that the `uniqueString()` function returns is the same whenever the template is deployed in the same resource group in the same Azure subscription.
41
-
- content: When the template is deployed to the same resource group in the same subscription repeatedly, the `siteName` parameter's default value will be the same each time.
42
-
isCorrect: true
43
-
explanation: Correct. The `siteName` parameter's default value uses string interpolation to combine the string prefix `mysite-` with a value from the `uniqueString()` function, which is seeded with the resource group ID. The value that the `uniqueString()` function returns is the same whenever the template is deployed in the same resource group in the same Azure subscription.
44
-
- content: The Bicep template that the IT department wrote has two modules in it. Which of these statements is true?
45
-
choices:
46
-
- content: If an output is added to one of the modules, it's automatically published as an output from the parent template too.
47
-
isCorrect: false
48
-
explanation: Incorrect. Outputs that Bicep modules define are available to the parent template, but they aren't automatically available to the template deployer. However, you can define an output in your template and pass the value through.
49
-
- content: If an output is added to one of the modules, it will automatically be available for the parent template to use.
50
-
isCorrect: true
51
-
explanation: Correct. The outputs from modules are automatically made available for the parent template to use, such as in defining input parameter values for other modules or in setting the properties on resources.
52
-
- content: Modules can't have outputs; only templates can.
53
-
isCorrect: false
54
-
explanation: Incorrect. Modules can define outputs. The outputs from modules are automatically made available to the parent template.
- content: What's the best way for the team to create a file that deploys to both test and production environments?
20
+
choices:
21
+
- content: Create a file that deploys all of the resources for the manufacturing application. Add file parameters for the values that might change between environments.
22
+
isCorrect: true
23
+
explanation: Correct. File parameters are a great way to manage multiple environments. You can specify different values for the parameters when you deploy the file into the test and production environments.
24
+
- content: Create a module that deploys all of the resources for the manufacturing application. Create separate Bicep files for each environment, and add the shared module to each environment's file.
25
+
isCorrect: false
26
+
explanation: Incorrect. Modules can be a great way to reuse your Bicep code, but when you're deploying multiple environments, there's usually a simpler way to keep track of the different configurations for each deployment.
27
+
- content: Create a file that deploys all of the resources required for the manufacturing application. Add variables for the values that might change between environments.
28
+
isCorrect: false
29
+
explanation: Incorrect. Variables have the same value, so you don't usually need to consider them when you deploy multiple environments.
30
+
- content: |
31
+
The file that the team has developed includes this line:<br />
- content: Whoever deploys the file must specify a value for the `siteName` parameter.
36
+
isCorrect: false
37
+
explanation: Incorrect. The `siteName` parameter has a _default value_ specified, which means that deployments don't have to specify the parameter value. If they don't, the parameter's default value is used.
38
+
- content: The `siteName` parameter will have a different default value every time the file is deployed.
39
+
isCorrect: false
40
+
explanation: Incorrect. The parameter's default value is set through the `uniqueString()` function, which has been seeded with the resource group's ID. Therefore, the value that the `uniqueString()` function returns is the same whenever the file is deployed in the same resource group in the same Azure subscription.
41
+
- content: When the file is deployed to the same resource group in the same subscription repeatedly, the `siteName` parameter's default value will be the same each time.
42
+
isCorrect: true
43
+
explanation: Correct. The `siteName` parameter's default value uses string interpolation to combine the string prefix `mysite-` with a value from the `uniqueString()` function, which is seeded with the resource group ID. The value that the `uniqueString()` function returns is the same whenever the file is deployed in the same resource group in the same Azure subscription.
44
+
- content: The Bicep file that the IT department wrote has two modules in it. Which of these statements is true?
45
+
choices:
46
+
- content: If an output is added to one of the modules, it's automatically published as an output from the parent file too.
47
+
isCorrect: false
48
+
explanation: Incorrect. Outputs that Bicep modules define are available to the parent file, but they aren't automatically available to the file deployer. However, you can define an output in your file and pass the value through.
49
+
- content: If an output is added to one of the modules, it will automatically be available for the parent file to use.
50
+
isCorrect: true
51
+
explanation: Correct. The outputs from modules are automatically made available for the parent file to use, such as in defining input parameter values for other modules or in setting the properties on resources.
52
+
- content: Modules can't have outputs; only files can.
53
+
isCorrect: false
54
+
explanation: Incorrect. Modules can define outputs. The outputs from modules are automatically made available to the parent file.
Copy file name to clipboardExpand all lines: learn-pr/azure/build-first-bicep-template/includes/1-introduction.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,18 +8,18 @@ You'll host the website in Azure using Azure App Service. You'll incorporate a s
8
8
9
9
:::image type="content" source="../media/1-architecture-diagram.png" alt-text="Architecture diagram that shows a resource group containing an App Service plan, App Service app, and storage account." border="false":::
10
10
11
-
You decide to build the resources using infrastructure as code (IaC) techniques so you can reuse the template for future product launches.
11
+
You decide to build the resources using infrastructure as code (IaC) techniques so you can reuse the file for future product launches.
12
12
13
13
## What will we learn?
14
14
15
-
In this module, you'll create a reusable Bicep template to deploy a set of Azure resources for new product launches. You'll use many elements of the Bicep language, including:
15
+
In this module, you'll create a reusable Bicep file to deploy a set of Azure resources for new product launches. You'll use many elements of the Bicep language, including:
16
16
17
17
- Resource definitions to deploy your Azure resources from your Bicep code.
18
-
- Parameters to make your template reusable.
19
-
- Variables and expressions to make it easier to write and deploy your template.
20
-
- Modules to help structure your template into multiple files.
21
-
- Outputs to send data from your template and modules back to whoever or whatever is deploying your infrastructure.
18
+
- Parameters to make your file reusable.
19
+
- Variables and expressions to make it easier to write and deploy your file.
20
+
- Modules to help structure your file into multiple files.
21
+
- Outputs to send data from your file and modules back to whoever or whatever is deploying your infrastructure.
22
22
23
23
## What is the main goal?
24
24
25
-
By the end of this module, you'll be able to create Bicep templates that define your Azure resources. You'll be able to use parameters, variables, and expressions to make your templates reusable. You'll also be able to use modules and outputs to organize your templates into separate files.
25
+
By the end of this module, you'll be able to create Bicep files that define your Azure resources. You'll be able to use parameters, variables, and expressions to make your files reusable. You'll also be able to use modules and outputs to organize your files into separate files.
0 commit comments