更新时间: 试题数量: 购买人数: 提供作者:

有效期: 个月

章节介绍: 共有个章节

收藏
搜索
题库预览
Case Study 

1 - Litware (QUESTION 1 - QUESTION 5) 

Overview 

Existing Environment 

Litware, Inc. e 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.NET web forms that use logic written in VB.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 live 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 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. 

Customers report that bug reporting is overly complex. 

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 existing retirement fund 

management system. 

The investment planning applications suite will include one multi-tier web application and two iOS 

mobile application. 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 packages. 

Litware has started an internal cloud transformation process and plans to use cloud-based 

services whenever suitable. 

Litware wants to become proactive in detecting failures, rather than always waiting for customer 

bug reports. 

Technical requirements 

The company’s investment planning applications suite must meet the following 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 releases must remain available for 30 days, except for production releases, which 

must be kept for 60 days. 

= 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 HTTPS. 

= The required operating system configuration for the test servers changes weekly. Azure 

Automation State Configuration must be used to ensure that the operating system on each 

test server is configured the same way when the servers are created and checked 

periodically. 

Current Technical Issue 

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. 

(含图)


QUESTION 1 

To resolve the current technical issue, what should you do to the Register

AzureRmAutomationDscNode command? 

Case Study 2 - Contoso, Ltd (QUESTION 6 - QUESTION 11) 

Background 

Contoso, Ltd. is a manufacturing company that has a main office in Chicago. 

Contoso plans to improve its IT development and operations processes by implementing Azure 

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 Pool? that contains 10 Azure virtual machines that run Windows 

Server 2016 

The Azure subscription contains an Azure Automation account. 

Contoso plans to create projects in Azure DevOps as shown in the following table. 

(含图)

Technical requirements 

Contoso identifies the following technical requirements: 

= Implement build agents for Projectt. 

= Whenever possible, use Azure resources. 

= Avoid using deprecated technologies. 

= Implement a code flow strategy for Project2 that will: 

- Enable Team2 to submit pull requests for Project2. 

- Enable Team2 to work independently on changes to a copy of Project2. 

- Ensure that any intermediary changes performed by Team2 on a copy of Project2 will be subject 

to the same restrictions as the ones defined in the build policy of Project2. 

= Whenever possible implement automation and minimize administrative effort. 

= Implement Project3, Project5, Project6, and Project/ based on the planned changes 

= Implement Project4 and configure the project to push Docker images to Azure Container 

Registry. 


QUESTION 6 

You add the virtual machines as managed nodes in Azure Automation State Configuration. 

You need to configure the computer in Group/. 

What should you do? 

1 2