Explanation

Box 1: No
Azure resources deployed to a single resource group can be located in different regions. The resource group only contains metadata about the resources it contains.
When creating a resource group, you need to provide a location for that resource group. You may be wondering, "Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?" The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.
Box 2: No
Tags for Resources are not inherited by default from their Resource Group Box 3: Yes A resource group can be used to scope access control for administrative actions. By default, permissions set at the resource level are inherited by the resources in the resource group.

Explanation:
Azure Cosmos DB is an example of a platform as a service (PaaS) cloud database provider.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/database-security

Azure Databricks is an Apache Spark-based analytics platform. The platform consists of several components including 'MLib'. Mlib is a Machine Learning library consisting of common learning algorithms and utilities, including classification, regression, clustering, collaborative filtering, dimensionality reduction, as well as underlying optimization primitives.
References:
https://docs.microsoft.com/en-us/azure/azure-databricks/what-is-azure-databricks#apache-spark-based-analytics-platform

Section: Describe identity, governance, privacy, and compliance features Explanation/Reference:
https://docs.microsoft.com/en-us/azure/governance/policy/overview