See explanation below
Explanation:
Step 1: Log in to the Azure Portal
* Go to https://portal.azure.com .
* Log in with your Azure account.
Step 2: Create an Azure App Configuration Instance
* In the search bar at the top, type "App Configuration" and select App Configuration from the search results.
* Click + Create .
* Fill in the required fields:
* Subscription: Your Azure subscription.
* Resource Group: Create a new one or select an existing one.
* Name: Provide a globally unique name (for example, myappconfig-instance).
* Location: Choose a region close to your application.
* Click Review + Create , then Create .
The instance will take a few seconds to deploy.
Step 3: Access the App Configuration Instance
* Once the deployment is complete, click Go to resource .
* You are now in the App Configuration resource.
Step 4: Enable Feature Management
* In the left menu, click on Feature Manager (Preview) .
* Click + Add to create a new feature flag.
Step 5: Create the Feature Flag
* Provide the following details:
* Feature flag name: feature1
* Label: (optional)
* Description: (optional)
* State: Set to Enabled .
* Click on the Add filters link if you want to add targeting filters (optional).
* Click Save to create the feature flag.
Step 6: Set the Expiration Date for the Feature Flag
* In the Feature Manager list, find the newly created feature1 flag.
* Click on the three dots (context menu) next to feature1 and select Edit .
* In the Edit feature pane, look for the Expiration date setting. If there is no direct UI for expiration date, you can store it as a custom key-value (metadata).
Here's how to store expiration as metadata:
* In the App Configuration left menu, click on Configuration Explorer .
* Locate the key: .appconfig.featureflag/feature1.
* Click on the key to edit.
* Add a new label or add a custom key in the Content type or tags section to store expiration metadata:
* Key: expiration
* Value: yyyy-MM-dd (set to today + 7 days)
For example, if today is June 4, 2025, set the expiration as 2025-06-11.

Explanation:
Graphical user interface, text, application Description automatically generated

Woodgrove Bank identifies the following technical requirements:
* The Azure DevOps dashboard must display the metrics shown in the following table:

Box 1: Velocity
Velocity displays your team velocity. It shows what your team delivered as compared to plan.
Box 2: Release pipeline overview
Release pipeline overview shows the status of environments in a release definition.
Box 3: Query tile
Query tile displays the total number of results from a query.
Reference:
https://docs.micros oft.com/en-us/azure/devops/report/dashboards/widget-catalog?view=azure-devops

See the explanation for answer below.
Explanation:
Answer is as:

Use two templates, one for each resource group, and link the templates.
References:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-linked-templates

Explanation:
1 - > TFVS Refer : https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/control-access-team-foundation- version-control?view=azure-devops
2 - > TFVS Refer : https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/add-check-policies?view=azure- devops
3 - > Git Refer : https://docs.microsoft.com/en-us/azure/devops/repos/git/share-your-code-in-git-xcode?
view=azure-devops
4 - > TFVS Refer :https://docs.microsoft.com/en-us/azure/devops/organizations/security/permissions?
view=azure-devops#tfvc