Refer to the exhibit. You are reviewing the configuration of an Azure OpenAI Service resource. The resource is configured with customer-managed keys for encryption. What is the primary benefit of this configuration?
Customer-managed keys let you supply and rotate your own Key Vault key, so Microsoft cannot decrypt the data. This satisfies the requirement for control over the encryption key lifecycle, rather than relying on Microsoft-managed keys.
Why this answer
Customer-managed keys (CMK) allow you to control and manage the encryption keys used to protect your data at rest in Azure OpenAI Service. This provides enhanced control over who can access the keys, when they are rotated, and how they are stored, which is critical for meeting compliance and security requirements. The primary benefit is not performance, cost, or deployment simplicity, but rather the ability to enforce your own key lifecycle and access policies.
Exam trap
The trap here is that candidates often confuse customer-managed keys with platform-managed keys, assuming the primary benefit is cost savings or performance gains, when in reality the core advantage is granular control over encryption key governance and compliance.
How to eliminate wrong answers
Option B is wrong because customer-managed keys add complexity to the deployment process (you must create and manage a Key Vault, set permissions, and configure key rotation), not simplify it. Option C is wrong because encryption keys have no impact on model inference speed or accuracy; performance is determined by model size, token limits, and compute resources. Option D is wrong because CMK typically increases operational costs due to the need for additional Key Vault resources, key management overhead, and potential charges for key operations.