AZ-500 · Question #551
Case Study 4 - Fabrikam, Inc Overview Fabrikam, Inc. is a consulting company. The company has a main office in New York City and branch offices in Amsterdam and Singapore. Existing Environment…
The correct answer is B. Create an encryption scope in storage2. Explanation Option B is correct because an encryption scope in Azure Storage allows you to apply customer-managed keys (Fabrikam-managed keys) at a granular level within a storage account, and crucially, Azure Table storage requires an encryption scope to support…
Question
Options
- AEnable purge protection for storage2.
- BCreate an encryption scope in storage2.
- CAssign an Azure role-based access control (Azure RBAC) role to storage2.
- DConfigure storage2 to use an account encryption key
How the community answered
(29 responses)- A14% (4)
- B72% (21)
- C10% (3)
- D3% (1)
Explanation
Explanation
Option B is correct because an encryption scope in Azure Storage allows you to apply customer-managed keys (Fabrikam-managed keys) at a granular level within a storage account, and crucially, Azure Table storage requires an encryption scope to support customer-managed keys - it cannot use account-level customer-managed key encryption directly like Blob storage can.
Option A (Purge protection) is incorrect because purge protection is a Key Vault feature that prevents permanent deletion of keys/secrets; it does not configure storage encryption with customer-managed keys.
Option C (RBAC role assignment) is incorrect because assigning an RBAC role controls access permissions to storage resources, not how the data at rest is encrypted using Fabrikam-managed keys.
Option D (Account encryption key) is incorrect because while account-level customer-managed key encryption works for Blob and Queue storage, Table storage specifically requires an encryption scope to use customer-managed keys - this is a key Azure limitation to remember.
Memory Tip: Think "Table = Scope" - Azure Table storage is the exception that requires an encryption scope (rather than an account-level key) when using customer-managed keys. If you see Table storage + customer-managed keys on the exam, encryption scope is always the answer.
Topics
Community Discussion
No community discussion yet for this question.