Which statement applies when enabling multitenancy in Prisma Access (Managed by Panorama)?

The defining architectural principle of Prisma Access multitenancy under Panorama management is resource isolation: when multitenancy is enabled on a Panorama appliance, each tenant that is subsequently created is provisioned with its own dedicated Prisma Access instance, and the underlying compute resources backing that instance are not shared with any other tenant hosted on the same Panorama. This isolation is what allows an MSSP-style or business-unit-segmented deployment to guarantee that one tenant ' s traffic volume, performance, or configuration issues cannot bleed into another ' s environment, and it is stated as such in the platform ' s own multitenancy documentation, making option C the correct statement. Option A is incorrect because licensing in a multitenant deployment is allocated per tenant out of the overall license pool as tenants are created, not concentrated exclusively on the first tenant with sharing extended to others — each tenant draws its own bandwidth and user allocation. Option B is incorrect; a single tenant can be configured with mobile users only, remote networks only, or a combination of both, as long as it meets the minimum license allocation for whichever component it uses. Option D misrepresents the architecture: multitenancy, by definition, consolidates management of all tenants under a single Panorama appliance (or an HA pair); running separate Panoramas per tenant is a distinct architectural choice unrelated to, and not what, the multitenancy feature itself provides.