An IT manager is evaluating a cloud storage service for backup of critical company data. The manager is concerned about data security and availability. The service offers encryption at rest and in transit, 99.9% uptime SLA, and geo-redundancy. However, the service uses multi-tenancy. Which of the following is a potential concern the manager should address?
Multi-tenancy increases the risk of data leakage if proper isolation fails.
Why this answer
The primary concern with multi-tenancy in a cloud storage service is the risk of data isolation failure, where a vulnerability or misconfiguration could allow one tenant to access another tenant's data. Even with strong encryption at rest and in transit, the data must be decrypted for processing, and if the hypervisor or storage layer has a flaw, other tenants could potentially read the decrypted data. This is a well-known security risk in shared infrastructure models like IaaS and PaaS.
Exam trap
The trap here is that candidates may focus on encryption or SLA metrics as the main security concern, overlooking the fundamental risk of data leakage in a shared multi-tenant architecture, which is a core concept in cloud computing security models.
How to eliminate wrong answers
Option A is wrong because a 99.9% uptime SLA (approximately 8.76 hours of downtime per year) is generally considered sufficient for most critical data backup scenarios, and the question does not specify a higher requirement. Option B is wrong because encryption overhead from AES-256 or TLS 1.3 is negligible on modern hardware and does not typically cause noticeable slowdowns for backup data transfers. Option C is wrong because geo-redundancy replicates data asynchronously to a secondary region, and while it may introduce slight write latency, it does not affect read latency for the primary copy and is a standard feature for disaster recovery.