You use Calendar Versioning (CalVer) for code assets.
You need to store an optional tag of beta as part of the version.
Which part of the version should you use for the tag?
A. minor
B. major
C. micro
D. modifier
Show Answer
Correct Answer: D
Explanation: In Calendar Versioning (CalVer), the optional text suffix used for prerelease identifiers such as 'alpha', 'beta', 'rc1', or 'dev' is the modifier component. Therefore, to store an optional 'beta' tag, use the modifier part of the version.
Question 166
You have a project in Azure DevOps named Project1 that contains two environments named environment1 and environment2.
When a new version of Project is released, the latest version is deployed to environment2, and the previous version is redeployed to environment1.
You need to distribute users across the environments. The solution must meet the following requirements:
• New releases must be available to only a subset of the users.
• You must gradually increase the number of users that can access environment2.
What should you use?
A. VIP swaping
B. web app deployment slots
C. Azure Load Balancer
D. Azure Traffic Manager
Show Answer
Correct Answer: B
Explanation: Use Azure App Service deployment slots. Deployment slots support gradual exposure of a new version by configuring traffic routing percentages to a slot, enabling canary-style releases where only a subset of users initially receive the new version and the percentage is increased over time. Traffic Manager distributes DNS traffic across endpoints but is not the feature intended for gradual percentage-based rollout between application versions in deployment slots.
Question 167
DRAG DROP
-
You have an Azure Pipeline.
You need to store configuration values as variables.
At which four scopes can the variables be defined, and what is the precedence of the variables from the highest precedence to lowest precedence? To answer, move the appropriate scope from the list of scopes to the answer area and arrange them in the correct order.
Explanation: Azure Pipelines YAML variable precedence (highest to lowest) is: job, stage, pipeline root, then pipeline settings UI. 'Task' is not a valid variable definition scope in YAML.
Question 168
HOTSPOT
-
You have an Azure subscription that contains two resource groups named ContosoRG and ContosoDev, an Azure data factory named Contoso Data Factory, and a release pipeline in Azure Pipelines named Pipeline1.
You plan to deploy Contoso Data Factory to ContosoRG by using Pipeline1.
You add the Azure Resource Manager (ARM) template deployment task shown in the following exhibit.
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Deployment mode
output of the continuous integration build
Explanation: Complete mode can remove resources not in the template; Incremental deployment mode avoids modifying unrelated existing resources. With Template location set to Linked artifact, the ARM template is retrieved from the build artifact produced by the continuous integration build.
Question 169
HOTSPOT
-
You use Git for source control. You have an app named App1.
In the main branch, you need to restore the third most recent revision of a file named App.exe.config.
How should you complete the command? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: checkout
--source
Explanation: Use `git checkout main` to ensure you are on the main branch, then `git restore --source=main~3 App.exe.config` to restore the file from the third most recent commit on the main branch.
Question 170
DRAG DROP
-
You are designing a versioning strategy for Git-based packages.
You plan to use a Semantic Versioning (SemVer)-based strategy.
You need to identify when to change the build version.
What should you identify for each scenario? To answer, drag the appropriate versions to the correct scenarios. Each version may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: You rename a parameter in an API: Major
You deprecate functionality in an API: Minor
You add a feature and maintain backwards compatibility: Minor
Explanation: Under Semantic Versioning: breaking API changes require a major version bump; marking functionality as deprecated is a backward-compatible API change and increments the minor version; adding backward-compatible functionality also increments the minor version.
Question 171
DRAG DROP
-
You have a GitHub repository that contains the code for an app named App1.
App1 depends on a library of functions from a repository at https://github.com/contoso/afeed.
You need to keep a clone of the afeed repository as a subdirectory of the App1 repository.
How should you complete the Git command? To answer, drag the appropriate values to the correct targets. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: submodule
add
Explanation: To keep another Git repository as a subdirectory while maintaining its own history, use a Git submodule. The command is `git submodule add <repository-url>`.
Question 172
DRAG DROP
-
You have an Azure subscription that uses Azure Automation State Configuration to manage the configuration of virtual machines.
You need to identify which nodes are noncompliant.
How should you complete the query? To answer, drag the appropriate values to the correct targets. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Category
OperationName
ResultType
Explanation: Use the AzureDiagnostics query filters for DSC node compliance: Category == "DscNodeStatus", OperationName contains the DSC node status operation, and ResultType != "Compliant" to identify noncompliant nodes.
Question 173
You have an Azure DevOps project that produces Node Package Manager (npm) packages. Multiple projects consume the packages.
You need to configure Azure Artifacts to ensure that both the latest and pre-release versions of the packages are available for consumption.
What should you do?
A. Create two feed views named @prerelease and @release, Set @release as the default view. Configure a release pipeline that tags the packages as release after successful testing.
B. Create a feed view named @prerelease. Configure a release pipeline that tags the packages as release after successful testing.
C. Create two feed views named @prerelease and @default. Configure a release pipeline that promotes a package to the @default view after successful testing.
D. Create two feed views named @prerelease and @release. Set @release as the default view. Configure a release pipeline that promotes a package to the @release view after successful testing.
Show Answer
Correct Answer: D
Explanation: Azure Artifacts feed views are intended to separate package maturity. A common pattern is to use @prerelease and @release views, with consumers using the default @release view for stable packages. Packages are first published, then promoted (not tagged) to the appropriate view after validation. After successful testing, the release pipeline should promote the package to the @release view so both prerelease and stable versions remain available.
Question 174
HOTSPOT
-
You company uses a Git source-code repository.
You plan to implement GitFlow as a workflow strategy.
You need to identify which branch types are used for production code and preproduction code in the strategy.
Which branch type should you identify for each code type? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Production code: Main
Preproduction code: Develop
Explanation: In the GitFlow workflow, the Main branch contains production-ready code, while the Develop branch integrates completed features and serves as the preproduction/staging branch. Feature branches are used for individual feature development.
$19
Get all 534 questions with detailed answers and explanations
Instant download HTML + PDF delivered the moment payment clears.
Secure Stripe checkout we never see or store your card details.
7-day refund if files are defective see our refund policy.