[
  {
    "id": "cs-1",
    "title": "Topic 1, Case Study 1",
    "questionIds": [
      555,
      556,
      557,
      570,
      583
    ],
    "body": {
      "en": "Case Study\nThis is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete\neach case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure\nthat you are able to complete all questions included on this exam in the time provided.\nTo answer the questions included in a case study, you will need to reference information that is provided in the case study.\nCase studies might contain exhibits and other resources that provide more information about the scenario that is described\nin the case study. Each question is independent of the other questions in this case study.\nAt the end of this case study, a review screen will appear. This screen allows you to review your answers and to make\nchanges before you move to the next section of the exam. After you begin a new section, you cannot return to this section.\nTo start the case study\nTo display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of\nthe case study before you answer the questions. Clicking these buttons displays information such as business requirements,\nexisting environment, and problem statements. If the case study has an All Information tab, note that the information\ndisplayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click\nthe Question button to return to the question.\nOverview\nContoso, Ltd. is a manufacturing company that has a main office in Chicago.\nExisting Environment\nContoso plans to improve its IT development and operations processes by implementing Azure DevOps principles. Contoso\nhas an Azure subscription and creates an Azure DevOps organization.\nThe Azure DevOps organization includes:\nThe Docker extension\n\nA deployment pool named Pool7 that contains 10 Azure virtual machines that run Windows Server 2019\n\nThe Azure subscription contains an Azure Automation account.\nRequirements\nPlanned changes\nContoso plans to create projects in Azure DevOps as shown in the following table.\n\n\nTechnical requirements\nContoso identifies the following technical requirements:\nImplement build agents for Project1.\n\nWhenever possible, use Azure resources.\n\nAvoid using deprecated technologies.\n\nImplement a code flow strategy for Project2 that will:\n\n- Enable Team2 to submit pull requests for Project2.\n- Enable Team2 to work independently on changes to a copy of Project2.\n- Ensure that any intermediary changes performed by Team2 on a copy of Project2 will be subject to the same restrictions as\nthe ones defined in the build policy of Project2. Whenever possible, implement automation and minimize administrative\n\neffort.\nImplement Project3, Project5, Project6, and Project7 based on the planned changes.\n\nImplement Project4 and configure the project to push Docker images to Azure Container Registry.\n",
      "vi": ""
    },
    "images": [
      "assets/az-400/case-studies/cs-1/img-0.png"
    ]
  },
  {
    "id": "cs-2",
    "title": "Topic 2, Case Study 2",
    "questionIds": [
      558,
      559,
      560,
      592
    ],
    "body": {
      "en": "Case Study\nThis is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete\neach case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure\nthat you are able to complete all questions included on this exam in the time provided.\nTo answer the questions included in a case study, you will need to reference information that is provided in the case study.\nCase studies might contain exhibits and other resources that provide more information about the scenario that is described\nin the case study. Each question is independent of the other questions in this case study.\nAt the end of this case study, a review screen will appear. This screen allows you to review your answers and to make\nchanges before you move to the next section of the exam. After you begin a new section, you cannot return to this section.\nTo start the case study\nTo display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of\nthe case study before you answer the questions. Clicking these buttons displays information such as business requirements,\nexisting environment, and problem statements. If the case study has an All Information tab, note that the information\ndisplayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click\nthe Question button to return to the question.\nOverview\nLitware, Inc. is an independent software vendor (ISV). Litware has a main office and five branch offices.\nExisting Environment\nApplication Architecture\nThe companys primary application is a single monolithic retirement fund management system based on ASP.NET web\nforms that use logic written in VB.NET. Some new sections of the application are written in C#.\nVariations of the application are created for individual customers. Currently, there are more than 80 live code branches in the\napplications code base.\nThe application was developed by using Microsoft Visual Studio. Source code is stored in Team Foundation Server (TFS) in\nthe main office. The branch offices access the source code by using TFS proxy servers.\nArchitectural Issues\nLitware focuses on writing new code for customers. No resources are provided to refactor or remove existing code. Changes\nto the code base take a long time, as dependencies are not obvious to individual developers.\nMerge operations of the code often take months and involve many developers. Code merging frequently introduces bugs\nthat are difficult to locate and resolve.\nCustomers report that ownership costs of the retirement fund management system increase continually. The need to merge\nunrelated code makes even minor code changes expensive.\nCustomers report that bug reporting is overly complex.\nRequirements\nPlanned Changes\nLitware plans to develop a new suite of applications for investment planning. The investment planning applications will\nrequire only minor integration with the existing retirement fund management system.\nThe investment planning applications suite will include one multi-tier web application and two iOS mobile applications. One\nmobile application will be used by employees; the other will be used by customers.\nLitware plans to move to a more agile development methodology. Shared code will be extracted into a series of packages.\nLitware has started an internal cloud transformation process and plans to use cloud-based services whenever suitable.\nLitware wants to become proactive in detecting failures, rather than always waiting for customer bug reports.\nTechnical Requirements\nThe companys investment planning applications suite must meet the following technical requirements:\nNew incoming connections through the firewall must be minimized.\n\nMembers of a group named Developers must be able to install packages.\n\nThe principle of least privilege must be used for all permission assignments.\n\nA branching strategy that supports developing new functionality in isolation must be used.\n\nMembers of a group named Team Leaders must be able to create new packages and edit the permissions of package\n\nfeeds.\nVisual Studio App Center must be used to centralize the reporting of mobile application crashes and device types in use.\n\nBy default, all releases must remain available for 30 days, except for production releases, which must be kept for 60 days.\n\nCode quality and release quality are critical. During release, deployments must not proceed between stages if any active\n\nbugs are logged against the release.\nThe mobile applications must be able to call the share pricing service of the existing retirement fund management system.\n\nUntil the system is upgraded, the service will only support basic authentication over HTTPS.\nThe required operating system configuration for the test servers changes weekly. Azure Automation State Configuration\n\nmust be used to ensure that the operating system on each test server is configured the same way when the servers are\ncreated and checked periodically.\nCurrent Technical Issue\nThe test servers are configured correctly when first deployed, but they experience configuration drift over time. Azure\nAutomation State Configuration fails to correct the configurations.\nAzure Automation State Configuration nodes are registered by using the following command.",
      "vi": ""
    },
    "images": [
      "assets/az-400/case-studies/cs-2/img-0.png"
    ]
  },
  {
    "id": "cs-3",
    "title": "Topic 3, Case Study 3",
    "questionIds": [
      561,
      562,
      563,
      580,
      581
    ],
    "body": {
      "en": "This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete\neach case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure\nthat you are able to complete all questions included on this exam in the time provided.\nTo answer the questions included in a case study, you will need to reference information that is provided in the case study.\nCase studies might contain exhibits and other resources that provide more information about the scenario that is described\nin the case study. Each question is independent of the other questions in this case study.\nAt the end of this case study, a review screen will appear. This screen allows you to review your answers and to make\nchanges before you move to the next section of the exam. After you begin a new section, you cannot return to this section.\nTo start the case study\nTo display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of\nthe case study before you answer the questions. Clicking these buttons displays information such as business requirements,\nexisting environment, and problem statements. If the case study has an All Information tab, note that the information\ndisplayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click\nthe Question button to return to the question. Overview\nGeneral Overview\nWoodgrove Bank is a financial services company that has a main office in the United Kingdom.\nTechnical Requirements and Planned Changes\nPlanned Changes\nWoodgrove Bank plans to implement the following project management changes:\nImplement Azure DevOps for project tracking.\n\nCentralize source code control in private GitHub repositories.\n\nImplement Azure Pipelines for build pipelines and release pipelines.\n\nWoodgrove Bank plans to implement the following changes to the identity environment:\nDeploy an Azure AD tenant named woodgrovebank.com.\n\nSync the Active Directory domain to Azure AD.\n\nConfigure App1 to use a service principal. Integrate GitHub with Azure AD.\n\n\nWoodgrove Bank plans to implement the following changes to the core apps:\nMigrate App1 to ASP.NET Core.\n\nIntegrate Azure Pipelines and the third-party build tool used to develop App2.\n\nWoodgrove Bank plans to implement the following changes to the DevOps environment:\nDeploy App1 to Azure App Service.\n\nImplement source control for the DB1 schema.\n\nMigrate all the source code from TFS1 to GitHub.\n\nDeploy App2 to an Azure virtual machine named VM1.\n\nMerge the POC branch into the GitHub default branch.\n\nImplement an Azure DevOps dashboard for stakeholders to monitor development progress. Technical Requirements\n\nWoodgrove Bank identifies the following technical requirements:\nThe initial databases for new environments must contain both schema and reference data.\n\nAn Azure Monitor alert for VM1 must be configured to meet the following requirements:\n\n- Be triggered when average CPU usage exceeds 80 percent for 15 minutes.\n- Calculate CPU usage averages once every minute.\nThe commit history of the POC branch must replace the history of the default branch. The Azure DevOps dashboard\n\n\nmust display the metrics shown in the following table.",
      "vi": ""
    },
    "images": [
      "assets/az-400/case-studies/cs-3/img-0.png"
    ]
  },
  {
    "id": "cs-4",
    "title": "Topic 4, Case Study 4",
    "questionIds": [
      551,
      552,
      553,
      554,
      586
    ],
    "body": {
      "en": "Case Study\nThis is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete\neach case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure\nthat you are able to complete all questions included on this exam in the time provided.\nTo answer the questions included in a case study, you will need to reference information that is provided in the case study.\nCase studies might contain exhibits and other resources that provide more information about the scenario that is described\nin the case study. Each question is independent of the other questions in this case study.\nAt the end of this case study, a review screen will appear. This screen allows you to review your answers and to make\nchanges before you move to the next section of the exam. After you begin a new section, you cannot return to this section.\nTo start the case study\nTo display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of\nthe case study before you answer the questions. Clicking these buttons displays information such as business requirements,\nexisting environment, and problem statements. If the case study has an All Information tab, note that the information\ndisplayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click\nthe Question button to return to the question.\nOverview\nContoso, Ltd. is a manufacturing company that has a main office in Chicago.\nExisting Environment\nContoso plans to improve its IT development and operations processes by implementing Azure DevOps principles. Contoso\nhas an Azure subscription and creates an Azure DevOps organization.\nThe Azure DevOps organization includes:\nThe Docker extension\n\nA deployment pool named Pool7 that contains 10 Azure virtual machines that run Windows Server 2019\n\nThe Azure subscription contains an Azure Automation account.\nRequirements\nPlanned changes\nContoso plans to create projects in Azure DevOps as shown in the following table.\n\nTechnical requirements\nContoso identifies the following technical requirements:\nImplement build agents for Project1.\n\nWhenever possible, use Azure resources.\n\nAvoid using deprecated technologies.\n\nImplement a code flow strategy for Project2 that will:\n\n- Enable Team2 to submit pull requests for Project2.\n- Enable Team2 to work independently on changes to a copy of Project2.\n- Ensure that any intermediary changes performed by Team2 on a copy of Project2 will be subject to the same restrictions as\nthe ones defined in the build policy of Project2. Whenever possible, implement automation and minimize administrative\n\neffort.\nImplement Project3, Project5, Project6, and Project7 based on the planned changes.\n\nImplement Project4 and configure the project to push Docker images to Azure Container Registry.",
      "vi": ""
    },
    "images": [
      "assets/az-400/case-studies/cs-4/img-0.png"
    ]
  },
  {
    "id": "cs-5",
    "title": "Topic 5, Case Study 5",
    "questionIds": [
      587,
      588,
      589,
      590,
      591
    ],
    "body": {
      "en": "Case Study\nThis is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete\neach case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure\nthat you are able to complete all questions included on this exam in the time provided.\nTo answer the questions included in a case study, you will need to reference information that is provided in the case study.\nCase studies might contain exhibits and other resources that provide more information about the scenario that is described\nin the case study. Each question is independent of the other questions in this case study.\nAt the end of this case study, a review screen will appear. This screen allows you to review your answers and to make\nchanges before you move to the next section of the exam. After you begin a new section, you cannot return to this section.\nTo start the case study\nTo display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of\nthe case study before you answer the questions. Clicking these buttons displays information such as business requirements,\nexisting environment, and problem statements. If the case study has an All Information tab, note that the information\ndisplayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click\nthe Question button to return to the question.\nOverview\nLitware, Inc. is an independent software vendor (ISV). Litware has a main office and five branch offices.\nExisting Environment\nApplication Architecture\nThe companys primary application is a single monolithic retirement fund management system based on ASP.NET web\nforms that use logic written in VB.NET. Some new sections of the application are written in C#.\nVariations of the application are created for individual customers. Currently, there are more than 80 live code branches in the\napplications code base.\nThe application was developed by using Microsoft Visual Studio. Source code is stored in Team Foundation Server (TFS) in\nthe main office. The branch offices access the source code by using TFS proxy servers.\nArchitectural Issues\nLitware focuses on writing new code for customers. No resources are provided to refactor or remove existing code. Changes\nto the code base take a long time, as dependencies are not obvious to individual developers.\nMerge operations of the code often take months and involve many developers. Code merging frequently introduces bugs\nthat are difficult to locate and resolve.\nCustomers report that ownership costs of the retirement fund management system increase continually. The need to merge\nunrelated code makes even minor code changes expensive.\nCustomers report that bug reporting is overly complex.\nRequirements\nPlanned Changes\nLitware plans to develop a new suite of applications for investment planning. The investment planning applications will\nrequire only minor integration with the existing retirement fund management system.\nThe investment planning applications suite will include one multi-tier web application and two iOS mobile applications. One\nmobile application will be used by employees; the other will be used by customers.\nLitware plans to move to a more agile development methodology. Shared code will be extracted into a series of packages.\nLitware has started an internal cloud transformation process and plans to use cloud-based services whenever suitable.\nLitware wants to become proactive in detecting failures, rather than always waiting for customer bug reports.\nTechnical Requirements\nThe companys investment planning applications suite must meet the following technical requirements:\nNew incoming connections through the firewall must be minimized.\n\nMembers of a group named Developers must be able to install packages.\n\nThe principle of least privilege must be used for all permission assignments.\n\nA branching strategy that supports developing new functionality in isolation must be used.\n\nMembers of a group named Team Leaders must be able to create new packages and edit the permissions of package\n\nfeeds.\nVisual Studio App Center must be used to centralize the reporting of mobile application crashes and device types in use.\n\nBy default, all releases must remain available for 30 days, except for production releases, which must be kept for 60 days.\n\nCode quality and release quality are critical. During release, deployments must not proceed between stages if any active\n\nbugs are logged against the release.\nThe mobile applications must be able to call the share pricing service of the existing retirement fund management system.\n\nUntil the system is upgraded, the service will only support basic authentication over HTTPS.\nThe required operating system configuration for the test servers changes weekly. Azure Automation State Configuration\n\nmust be used to ensure that the operating system on each test server is configured the same way when the servers are\ncreated and checked periodically.\nCurrent Technical Issue\nThe test servers are configured correctly when first deployed, but they experience configuration drift over time. Azure\nAutomation State Configuration fails to correct the configurations.\nAzure Automation State Configuration nodes are registered by using the following command.",
      "vi": ""
    },
    "images": [
      "assets/az-400/case-studies/cs-5/img-0.png"
    ]
  }
]