1 - Create a Desired State Configuration (DSC)configuration file that has an extension of .ps1.
2 - Run the Import-......
3 - Run the Start-.....
Topic 2, Litware inc.
Existing Environment
Litware, Inc. an independent software vendor (ISV) Litware has a main office and five branch offices.
Application Architecture
The company' s primary application is a single monolithic retirement fund management system based on ASP.NE T web forms that use logic written in V8.NET. Some new sections of the application are written in C#.
Variations of the application are created for individual customers. Currently, there are more than 80 have code branches in the application's code base.
The application was developed by using Microsoft Visual Studio. Source code is stored in Team Foundation Server (TFS) in the main office. The branch offices access of the source code by using TFS proxy servers.
Architectural Issues
Litware focuses on writing new code for customers. No resources are provided to refactor or remove existing code. Changes to the code base take a long time, AS dependencies are not obvious to individual developers.
Merge operations of the code often take months and involve many developers. Code merging frequently introduces bugs that are difficult to locate and resolve.
Customers report that ownership costs of the retirement fund management system increase continually. The need to merge unrelated code makes even minor code changes expensive.
Requirements
Planned Changes
Litware plans to develop a new suite of applications for investment planning. The investment planning Applications will require only minor integration with the easting retirement fund management system.
The investment planning applications suite will include one multi-tier web application and two iOS mobile applications. One mobile application will be used by employees; the other will be used by customers.
Litware plans to move to a more agile development methodology. Shared code will be extracted into a series of package.
Litware has started an internal cloud transformation process and plans to use cloud based services whenever suitable.
Litware wants to become proactive m detecting failures, rather than always waning for customer bug reports.
Technical Requirements
The company's investment planning applications suite must meet the following technical requirements:
* New incoming connections through the firewall must be minimized.
* Members of a group named Developers must be able to install packages.
* The principle of least privilege must be used for all permission assignments
* A branching strategy that supports developing new functionality in isolation must be used.
* Members of a group named Team leaders must be able to create new packages and edit the permissions of package feeds
* Visual Studio App Center must be used to centralize the reporting of mobile application crashes and device types in use.
* By default, all App Center must be used to centralize the reporting of mobile application crashes and device types in use.
* Code quality and release quality are critical. During release, deployments must not proceed between stages if any active bugs are logged against the release.
* The mobile applications must be able to call the share pricing service of the existing retirement fund management system. Until the system is upgraded, the service will only support basic authentication over HUPS.
* The required operating system configuration tor the test servers changes weekly. Azure Automation State Configuration must be used to ensure that the operating system on each test servers configured the same way when the servers are created and checked periodically.
Current Technical
The test servers are configured correctly when first deployed, but they experience configuration drift over time. Azure Automation State Configuration fails to correct the configurations.
Azure Automation State Configuration nodes are registered by using the following command.

Explanation

Box 1: Basic
Assign Basic to users with a TFS CAL, with a Visual Studio Professional subscription, and to users for whom you are paying for Azure Boards & Repos in an organization.
Box 2: Stakeholder
Assign Stakeholders to users with no license or subscriptions who need access to a limited set of features.
Note:
You assign users or groups of users to one of the following access levels:
Basic: provides access to most features
VS Enterprise: provides access to premium features
Stakeholders: provides partial access, can be assigned to unlimited users for free References: https://docs.microsoft.com/en-us/azure/devops/organizations/security/access-levels?view=vsts

Explanation
Instead reduce the code complexity.
Note: Technical debt is the accumulation of sub-optimal technical decisions made over the lifetime of an application. Eventually, it gets harder and harder to change things: it's the 'sand in the gears' that sees IT initiatives grind to a halt.
Reference:
https://dzone.com/articles/fight-through-the-pain-how-to-deal-with-technical
https://www.devopsgroup.com/blog/five-ways-devops-helps-with-technical-debt/

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
Topic 2, Contoso Case Study: 2
Overview
Existing Environment
Contoso, Ltd. is a manufacturing company that has a main office in Chicago.
Requirements
Contoso plans to improve its IT development and operations processes implementing Azue DevOps principles.
Contoso has an Azure subscription and creates an Azure DevOPs organization.
The Azure DevOps organization includes:
* The Docker extension
* A deployment pool named Pool7 that contains 10 Azure virtual machines that run Windows Server
2016.
The Azure subscription contains an Azure Automation account.
Planned Changes
Contoso plans to create projects in Azure DevOps as shown in the following table.

Technical Requirements
Contoso identities the following technical requirements:
* Implement build agents rot Project 1.
* Whenever possible, use Azure resources
*Avoid using deprecated technologies
* Implement a code flow strategy for Project2 that will:
*Enable Team 2 to submit pull requests for Project2.
* Enable Team 2 to work independently on changes to a copy of Project?
* Ensure that any intermediary changes performed by Tram2 on a copy of Project2 will be subject to the same restrictions as the ones defied in the build policy of Project2.
* Whenever possible. Implement automation and minimize administrative effort.
* Implement Protect3, Project5, Project6, and Project7 based on the planned changes.
* Implement Project4 and configure the project to push Docker images to Azure Container Reentry.

Explanation

Box 1; tag
Tagging. Like most VCSs, Git has the ability to tag specific points in a repository's history as being important.
Typically, people use this functionality to mark release points (v1.0, v2.0 and so on).
Box 2: -a
Creating an annotated tag in Git is simple. The easiest way is to specify -a when you run the tag command:
Example:
$ git tag -a v1.4 -m "my version 1.4"
Box 3: -m
Reference:
https://git-scm.com/book/en/v2/Git-Basics-Tagging