An IT team is deploying a new web application in Azure that consists of several virtual machines, a virtual network, and an Azure SQL database. The team wants to ensure that all these related assets can be managed together across their shared lifecycle, allowing administrators to deploy, configure access permissions, monitor, and delete them as a single logical unit. Which Azure architectural component should the team use to organize these resources?

Resource group: ### What an Azure Resource Group is An **Azure resource group** is a fundamental logical container designed to hold related Azure resources for an application or workload. Every Azure resource must exist inside exactly one resource group, serving as the core unit of lifecycle management within **Azure Resource Manager (ARM)**. ### How it meets the requirements - **Shared Lifecycle Management**: Grouping the web application's virtual machines, network, and database into a single resource group allows administrators to manage them collectively. When the workload needs updating, redeploying, or retiring, actions can be applied to the group as a whole. - **Simplified Administration and Deletion**: Deleting the resource group automatically deletes all nested resources, avoiding orphaned or unmonitored infrastructure. - **Access Control Scope**: Resource groups serve as a standard management boundary where **Azure role-based access control (Azure RBAC)** permissions can be assigned and automatically inherited by all member resources. ### Key advantages and capabilities - **Unified Deployment**: Works seamlessly with **ARM templates** and **Bicep** to deploy multi-tier architectures in a consistent, repeatable manner. - **Resource Metadata and Location**: Stores metadata describing the resources in a specific geographical region to meet compliance needs. - **Centralized Monitoring and Tagging**: Enables organization-wide monitoring, cost analysis, and policy enforcement at the container level. ### Why this is optimal A resource group is specifically designed to manage resources sharing an identical operational lifecycle, making it the most efficient architectural choice.