A software development company is planning to deploy its application for a new client.

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s deployment architectures, as taught in Pega Academy’sLead System Architect Missionand thePega Certified Lead System Architect Study Guide, include multitenancy, single tenancy, and variations like shared or isolated tenancy. Single tenancy is preferred when clients require full control over resources, security, and customization.

Option A (Incorrect): Multitenancy allows multiple clients to share the same Pega instance, which reduces resource control and may compromise security due to shared infrastructure. This is unsuitable for a client with unique security concerns, per thePega Cloud Architecturemodule.

Option B (Correct): Single tenancy provides a dedicated Pega instance for the client, ensuring full control over resources, security configurations, and performance optimizations. This aligns with the client’s need for customization and security, as documented in theDeployment Architecturesection of Pega Community.

Option C (Incorrect): Shared tenancy, a form of multitenancy, involves multiple clients sharing resources, which limits control and increases security risks. This is not ideal for the client’s requirements, per thePega Platform Architectureguidelines.

Option D (Incorrect): “Isolated tenancy” is not a standard Pega term. While it may imply a form of single tenancy, single tenancy is the precise and recognized architecture for dedicated resource control, as clarified in theDeployment Optionsmodule.