Your company is concerned that when developers introduce open source libraries, it creates licensing compliance issues.
You need to add an automated process to the build pipeline to detect when common open source libraries are added to the code base.
What should you use?

• A.Microsoft Visual SourceSafe
• B.Code Style
• C.Black Duck
• D.Jenkins
• E.SourceGea
• F.OWASP ZAP

Comment: *

Name: *

Email: *

Verification: *

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You integrate a cloud-hosted Jenkins server and a new Azure DevOps deployment.
You need Azure DevOps to send a notification to Jenkins when a developer commits changes to a branch in Azure Repos.
Solution: You create a service hook subscription that uses the code pushed event.
Does this meet the goal?

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

How should you configure the release retention policy for the investment planning applications suite? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

Explanation

Scenario: By default, all releases must remain available for 30 days, except for production releases, which must be kept for 60 days.
Box 1: Set the default retention policy to 30 days
The Global default retention policy sets the default retention values for all the build pipelines. Authors of build pipelines can override these values.
Box 2: Set the stage retention policy to 60 days
You may want to retain more releases that have been deployed to specific stages.
References: https://docs.microsoft.com/en-us/azure/devops/pipelines/policies/retention

Comment: *

Name: *

Email: *

Verification: *

You use Azure Pipelines lo manage the build and deployment of apps.
You are planning the release strategies for a new app. You need to choose strategies for the following scenarios:
* Releases will be made available to users who are grouped by their tolerance for software faults.
* Code will be deployed to enable functionality that will be available in later releases of the app.
* When a new release occurs, the existing deployment will remain active to minimize recovery time if a return to the previous version is required.

Correct Answer:

Explanation

Box 1: Progressive exposure
Continuous Delivery may sequence multiple deployment "rings" for progressive exposure (also known as
"controlling the blast radius"). Progressive exposure groups users who get to try new releases to monitor their experience in "rings." The first deployment ring is often a "canary" used to test new versions in production before a broader rollout. CD automates deployment from one ring to the next and may optionally depend on an approval step, in which a decision maker signs off on the changes electronically. CD may create an auditable record of the approval in order to satisfy regulatory procedures or other control objectives.

Box 2: Feature flags
Feature flags support a customer-first DevOps mindset, to enable (expose) and disable (hide) features in a solution, even before they are complete and ready for release.
Box 3: Blue/green
Blue/green deployments which means that instead of replacing the previous version (here we refer to this version as blue), we bring up the new version (here referred to as the green version) next to the existing version, but not expose it to the actual users right away. On the condition of having successfully validated that the green version works correctly, we will promote this version to the public version by changing the routing configuration without downtime. If something is wrong with the green version we can revert back without users every noticing interruptions.
Reference:
https://docs.microsoft.com/en-us/azure/devops/learn/what-is-continuous-delivery
https://docs.microsoft.com/en-us/azure/devops/migrate/phase-features-with-feature-flags
https://medium.com/@denniszielke/continuous-kubernetes-blue-green-deployments-on-azure-using-nginx-appga

Comment: *

Name: *

Email: *

Verification: *

You are designing a configuration management solution to support five apps hosted on Azure App Service.
Each app is available in the following three environments: development, test, and production.
You need to recommend a configuration management solution that meets the following requirements:
* Supports feature flags
* Tracks configuration changes from the past 30 days
* Stores hierarchically structured configuration values
* Controls access to the configurations by using role-based access control (RBAC) permission
* Stores shared values as key/value pairs that can be used by all the apps
Which Azure service should you recommend as the configuration management solution?

• A.Azure Cosmos DB
• B.Azure App Service
• C.Azure App Configuration
• D.Azure Key Vault

Comment: *

Name: *

Email: *

Verification: *