Several towns share one managed NoSQL service for 311 case documents. How should the platform isolate each town’s data at a basic tenancy level?
Select an answer to reveal the explanation.
Short Explanation
Shared NoSQL is fine if each town still has its own locker key. Put a tenant id in the partition or document key so Town A cannot casually walk into Town B’s cases. Same keys for everyone or one unkeyed blob is how isolation falls apart.
Full Explanation
Basic multi-tenant isolation on a shared NoSQL service commonly relies on tenant-scoped keys or partitions so reads and writes target only one customer’s data. Shared keys, disabled authentication, or a single unkeyed blob undermine logical isolation. Municipal 311 case stores should treat town identity as part of the access and keying design, not as an afterthought of full-text search.