nerdexam
Microsoft

AZ-400 · Question #302

Case Study 3 - Woodgrove Bank Overview General Overview Woodgrove Bank is a financial services company that has a main office in the United Kingdom. Technical Requirements and Planned Changes Planned

The correct answer is Threshold: Static; Operator: Greater than; Aggregation type *: Average; Aggregation granularity (Period) *: 5 minutes; Frequency of evaluation: Every 1 Minute. This hotspot question tests knowledge of Azure DevOps, GitHub integration, Azure Pipelines, and identity management within the context of Woodgrove Bank's planned migration and modernization efforts.

Submitted by naveen.iyer· Mar 6, 2026Implement an instrumentation strategy

Question

Case Study 3 - Woodgrove Bank Overview General Overview Woodgrove Bank is a financial services company that has a main office in the United Kingdom. Technical Requirements and Planned Changes Planned Changes Woodgrove Bank plans to implement the following project management changes: Implement Azure DevOps for project tracking. Centralize source code control in private GitHub repositories. Implement Azure Pipelines for build pipelines and release pipelines. Woodgrove Bank plans to implement the following changes to the identity environment: Deploy an Azure AD tenant named woodgrovebank.com. Sync the Active Directory domain to Azure AD. Configure App1 to use a service principal. Integrate GitHub with Azure AD. Woodgrove Bank plans to implement the following changes to the core apps: Migrate App1 to ASP.NET Core. Integrate Azure Pipelines and the third-party build tool used to develop App2. Woodgrove Bank plans to implement the following changes to the DevOps environment: Deploy App1 to Azure App Service. Implement source control for the DB1 schema. Migrate all the source code from TFS1 to GitHub. Deploy App2 to an Azure virtual machine named VM1. Merge the POC branch into the GitHub default branch. Implement an Azure DevOps dashboard for stakeholders to monitor development progress. Technical Requirements Woodgrove Bank identifies the following technical requirements: The initial databases for new environments must contain both schema and reference data. An Azure Monitor alert for VM1 must be configured to meet the following requirements: - Be triggered when average CPU usage exceeds 80 percent for 15 minutes. - Calculate CPU usage averages once every minute. The commit history of the POC branch must replace the history of the default branch. The Azure DevOps dashboard must display the metrics shown in the following table. Access to Azure DevOps must be restricted to specific IP addresses. Page load times for App1 must be captured and monitored. Administrative effort must be minimized. Hotspot Question You need to configure the alert for VM1. The solution must meet the technical requirements. Which two settings should you configure? To answer, select the appropriate settings in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibit

AZ-400 question #302 exhibit

Answer Area

  • ThresholdStatic
    StaticDynamic
  • OperatorGreater than
  • Aggregation type *Average
  • Threshold value *
  • Aggregation granularity (Period) *5 minutes
  • Frequency of evaluationEvery 1 Minute

Explanation

This hotspot question tests knowledge of Azure DevOps, GitHub integration, Azure Pipelines, and identity management within the context of Woodgrove Bank's planned migration and modernization efforts.

Approach. The correct approach requires understanding how each planned change maps to Azure DevOps capabilities and Azure AD integration. For source code migration, TFS1 content moves to private GitHub repositories, and Azure AD integration with GitHub enables SSO and security governance. App1 uses a service principal for authentication, which requires configuring Azure AD app registration, while App2 integrates with Azure Pipelines via a third-party build tool connector. DB1 schema source control is best handled using a dedicated database project in GitHub, enabling version-controlled schema changes through Azure Pipelines release pipelines targeting App Service and VM1 respectively.

Concept tested. Azure DevOps and GitHub integration planning - including source control migration from TFS to GitHub, Azure AD tenant setup and sync, service principal configuration, Azure Pipelines for CI/CD, and deploying applications to Azure App Service and Azure Virtual Machines. The question validates understanding of how identity, source control, build pipelines, and deployment targets interrelate in an enterprise DevOps transformation scenario.

Reference. Microsoft Learn: Migrate from TFVC to Git - https://learn.microsoft.com/en-us/azure/devops/repos/git/migrate-from-tfvc-to-git; Azure AD integration with GitHub - https://docs.github.com/en/organizations/managing-saml-single-sign-on-for-your-organization

Topics

#Azure Monitor#alert configuration#static threshold#CPU metrics

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-400 Practice