Identify the correct order of consolidation density, from worst to best.

Question

Options

• Amultitenant, schema consolidation, dedicated database, VMs
• Bschema consolidation, VMs, dedicated databases, multitenant
• Cdedicated databases, VMs, schema consolidation, multitenant
• DVMs, dedicated databases, schema consolidation, multitenant

• A
  13% (4)
• B
  6% (2)
• C
  3% (1)
• D
  77% (24)

Explanation

Oracle Multitenant on SuperCluster T5-8 Data centers today implement database consolidation predominantly using one of the following - databases in virtual machines (VMs) with typically one database per VM - multiple stacked single-instance databases (non-CDBs) on the same operating system - schema- or table-based consolidation inside the same database With databases in VMs, only the physical server is shared, but each database still requires its own operating system (OS) and database instance, resulting in poor resource utilization due to mostly static allocation of resources (i.e. CPU, memory). Consequently, both capital costs (as a result of low density) as well as operational costs (many OS and DB instances to manage) are high for such deployments. non-CDBs share a common OS, but still require dedicated database instances, which prevents the sharing of database structures such as buffer cache or background processes between them. It also does not reduce management costs significantly as databases are still administered individually (i.e. with respect to backup, restore, patching, and disaster recovery). Schema- and table-based consolidation, on the other hand maximizes sharing, but lacks isolation in terms of namespace, security, lifecycle, independent patching/upgrades, and performance and is in many cases not a suitable consolidation option. Oracle 12c introduces Oracle Multitenant, a new database consolidation model in which multiple Pluggable Databases (PDBs) are consolidated within a Container Database (CDB). While keeping many of the isolation aspects of single databases, it allows PDBs to share the system global area (SGA) and background processes of a common CDB. The multitenant architecture delivers the highest consolidation density without the overhead of changing application code and with improved security access controls. Standardization is easier than it has ever been. The failover of a container database, and its many pluggable databases, is faster than the fail over of a set of single dedicated databases. Oracle Database 12c supports up to 252 PDBs in a single CDB. In addition, up to 1024 Dynamic Database Services can be created on a given CDB, bringing greater economies of scale than consolidating dedicated databases on to a shared platform, or in individual VMs that are consolidated on to a shared server Schema Consolidation In this model the consolidated database consists of one or more application schemas running across one or more instances in a cloud pool. Customers who have implemented this approach typically limit the number of applications (schemas) to less than 20. The tenancy granularity is the

No community discussion yet for this question.