One HANA installation on a single EC2 instance must host separate development, quality and production databases, each with its own users, schemas and backup history and its own start and stop control, while sharing the host's CPU and memory. Which HANA capability delivers this?
Show answer and explanation
Answer: B
The multi-tenant database container lets one HANA installation run a system database plus multiple tenant databases. Each tenant has its own catalog, users, schemas, backup history and independent start and stop, so the environments stay logically separate while the host's CPU and memory are pooled under the global allocation limit. Consolidating environments this way reduces the number of EC2 instances and the administrative effort compared with one installation per system.
Why the other options are wrong
- A. Scale-out spreads one database across several nodes for capacity; it does not create isolated databases with separate administration.
- C. System replication copies one database to a standby for availability, so both sites hold the same data rather than separate environments.
- D. Dynamic tiering moves cold data to an extension node for cost reasons; it does not provide tenant isolation or separate backup histories.