Free Test
Question: / 10
Quiz
Question 1/101/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
To resolve the current technical issue, what should you do to theRegister-
AzureRmAutomationDscNodecommand?
AzureRmAutomationDscNodecommand?
Select the answer:Select the answer
1 correct answerA.
Change the value of theConfigurationModeparameter.
B.
Replace theRegister-AzureRmAutomationDscNodecmdlet withRegister- AzureRmAutomationScheduledRunbook
C.
Add theAllowModuleOverwriteparameter.
D.
Add theDefaultProfileparameter.
Quiz
Question 2/102/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
How should you confrere the release retention policy for the investment planning depletions suite?
To answer, select the appropriate options in the answer area.
NOTE: Eachcorrect selection is worth one point.
To answer, select the appropriate options in the answer area.
NOTE: Eachcorrect selection is worth one point.
Check the image below to see the right answer:Select the answer
1 correct answer
Every request made against a storage service must be authorized, unless the request is for a blob or
container resource that has been made available for public or signed access. One option for
authorizing a request is by using Shared Key.
Scenario: 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 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.
Reference:[https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key](https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key)
Quiz
Question 3/103/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
You need to configure a cloud service to store the secrets required by the mobile applications to call
the share.
What should you include in thesolution? To answer, select the appropriate options m the answer
area, NOTE: Each correct selection is worth one point.
the share.
What should you include in thesolution? To answer, select the appropriate options m the answer
area, NOTE: Each correct selection is worth one point.
Check the image below to see the right answer:Select the answer
1 correct answer
Every request made against a storage service must be authorized, unless the request is for a blob or
container resource that has been made available for public or signed access. One option for
authorizing a request is by using Shared Key.
Scenario: 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 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.
Reference:[https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key](https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key)
Quiz
Question 4/104/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
What should you use to implementthe code quality restriction on the release pipeline for the
investment planning applications suite?
investment planning applications suite?
Select the answer:Select the answer
1 correct answerA.
a trigger
B.
a pre deployment approval
C.
a post-deployment approval
D.
a deployment gate
Quiz
Question 5/105/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
How should youconfigure 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.
To answer, select the appropriate options in the answer area.
NOTE:Each correct selection is worth one point.
Check the image below to see the right answer:Select the answer
1 correct answer
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 defaultretention 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.
Reference:[https://docs.microsoft.com/en-us/azure/devops/pipelines/policies/retention](https://docs.microsoft.com/en-us/azure/devops/pipelines/policies/retention)
Quiz
Question 6/106/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Where should the build and release agents for the investment planning application suite run? To
answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Check the image below to see the right answer:Select the answer
1 correct answer
Box 1: A source control system
A source control system, also called a version control system, allows developers to collaborate on
code and track changes.Source control is an essential tool for multi-developer projects.
Box 2: A hosted service
To build and deploy Xcode apps or Xamarin.iOS projects, you'll need at least one macOS agent. If
your pipelines are in Azure Pipelines and a Microsoft-hosted agentmeets your needs, you can skip
setting up a self-hosted macOS agent.
Scenario: 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.
Reference:
[https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-osx?view=azure-devops](https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-osx?view=azure-devops)
Quiz
Question 7/107/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Which branching strategy should you recommend for the investment planning applications suite?
Select the answer:Select the answer
1 correct answerA.
release isolation
B.
main only
C.
development isolation
D.
feature isolation
Quiz
Question 8/108/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
DRAG DROP
Which package feed access levels should be assigned to the Developers and Team Leaders groups for
the investment planning applications suite? To answer, drag the appropriate access levels to the
correct groups. Each access level 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.
Which package feed access levels should be assigned to the Developers and Team Leaders groups for
the investment planning applications suite? To answer, drag the appropriate access levels to the
correct groups. Each access level 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.
Check the image below to see the right answer:Select the answer
1 correct answer
Box 1: Reader
Members of a group named Developers must be able to install packages.
Feeds have four levels of access: Owners, Contributors, Collaborators, and Readers. Ownerscan add
any type of identity-individuals, teams, and groups-to any access level.
Box 2: Owner
Members of a group named Team Leaders must be able to create new packages and edit the
permissions of package feeds.
Quiz
Question 9/109/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
You are using GitHub asa source code repository.
You create a client-side Git hook on the commit-msg event. The hook requires that each commit
message contain a custom work item tag.
You need to make a commit that does not have a work item tag.
Which git commit parameter shouldyou use?
You create a client-side Git hook on the commit-msg event. The hook requires that each commit
message contain a custom work item tag.
You need to make a commit that does not have a work item tag.
Which git commit parameter shouldyou use?
Select the answer:Select the answer
1 correct answerA.
--squash
B.
--no-verify
C.
--message ''
D.
--no-post-rewrite
Quiz
Question 10/1010/10
Topic 1, Litware inc. Case Study:1
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
Overview
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 systembased
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 andinvolve 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 areconfigured 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.
You have Azure Pipelines and GitHub integrated as a source code repository.
The build pipeline has continuous integration enabled.
You plan to trigger an automated build whenever code changes are committed to the repository.
You need to ensure that the system will wait until a build completes before queuing another build.
What should you implement?
The build pipeline has continuous integration enabled.
You plan to trigger an automated build whenever code changes are committed to the repository.
You need to ensure that the system will wait until a build completes before queuing another build.
What should you implement?
Select the answer:Select the answer
1 correct answerA.
path filters
B.
batch changes
C.
scheduled builds
D.
branch filters
Looking for more questions?Buy now
Microsoft Designing and Implementing Microsoft DevOps Solutions Practice test unlocks all online simulator questions
Thank you for choosing the free version of the Microsoft Designing and Implementing Microsoft DevOps Solutions practice test! Further deepen your knowledge on Microsoft Simulator; by unlocking the full version of our Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator you will be able to take tests with over 562 constantly updated questions and easily pass your exam. 98% of people pass the exam in the first attempt after preparing with our 562 questions.
BUY NOWWhat to expect from our Microsoft Designing and Implementing Microsoft DevOps Solutions practice tests and how to prepare for any exam?
The Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator Practice Tests are part of the Microsoft Database and are the best way to prepare for any Microsoft Designing and Implementing Microsoft DevOps Solutions exam. The Microsoft Designing and Implementing Microsoft DevOps Solutions practice tests consist of 562 questions and are written by experts to help you and prepare you to pass the exam on the first attempt. The Microsoft Designing and Implementing Microsoft DevOps Solutions database includes questions from previous and other exams, which means you will be able to practice simulating past and future questions. Preparation with Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator will also give you an idea of the time it will take to complete each section of the Microsoft Designing and Implementing Microsoft DevOps Solutions practice test . It is important to note that the Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator does not replace the classic Microsoft Designing and Implementing Microsoft DevOps Solutions study guides; however, the Simulator provides valuable insights into what to expect and how much work needs to be done to prepare for the Microsoft Designing and Implementing Microsoft DevOps Solutions exam.
BUY NOWMicrosoft Designing and Implementing Microsoft DevOps Solutions Practice test therefore represents an excellent tool to prepare for the actual exam together with our Microsoft practice test . Our Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator will help you assess your level of preparation and understand your strengths and weaknesses. Below you can read all the quizzes you will find in our Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator and how our unique Microsoft Designing and Implementing Microsoft DevOps Solutions Database made up of real questions:
Info quiz:
- Quiz name:Microsoft Designing and Implementing Microsoft DevOps Solutions
- Total number of questions:562
- Number of questions for the test:50
- Pass score:80%
You can prepare for the Microsoft Designing and Implementing Microsoft DevOps Solutions exams with our mobile app. It is very easy to use and even works offline in case of network failure, with all the functions you need to study and practice with our Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator.
Use our Mobile App, available for both Android and iOS devices, with our Microsoft Designing and Implementing Microsoft DevOps Solutions Simulator . You can use it anywhere and always remember that our mobile app is free and available on all stores.
Our Mobile App contains all Microsoft Designing and Implementing Microsoft DevOps Solutions practice tests which consist of 562 questions and also provide study material to pass the final Microsoft Designing and Implementing Microsoft DevOps Solutions exam with guaranteed success. Our Microsoft Designing and Implementing Microsoft DevOps Solutions database contain hundreds of questions and Microsoft Tests related to Microsoft Designing and Implementing Microsoft DevOps Solutions Exam. This way you can practice anywhere you want, even offline without the internet.
BUY NOW