1Z0-997-25 Question 84
Single answerYour organization is migrating a 10 TB on-premises Oracle Database to Oracle Cloud Infrastructure. The database workload supports large-scale analytics and business intelligence queries, which experience significant spikes in usage at month-end. They want to minimize administrative overhead, ensure robust security, and automatically handle changes in demand without requiring manual intervention. Which approach best satisfies these requirements?
- A
Provision an Autonomous Database (Data Warehouse workload) on Shared Infrastructure with auto-scaling enabled.
- B
Host your Oracle Database on a Bare Metal DB System and manually scale CPU resources during peak periods.
- C
Deploy a VM DB System across multiple Availability Domains with manual patching and backups.
- D
Use an Autonomous Database on Dedicated Infrastructure without enabling auto-scaling.
Show answer and explanation
Correct answer: A
Explanation
For large-scale analytics workloads with fluctuating demand, an Autonomous Database (especially configured as a Data Warehouse) on Shared Infrastructure aligns perfectly with the need for minimal manual management, robust security, and automated scaling. The Shared Infrastructure model reduces operational overhead by offloading capacity planning, patching, and maintenance to Oracle Cloud. Refer to the Oracle Cloud Infrastructure Database documentation for deeper insights into best practices and service capabilities.
- A. Correct.
This option is correct. An Autonomous Database (Data Warehouse workload) on Shared Infrastructure with auto-scaling offers the least administrative overhead and handles demand surges automatically. It also provides built-in security features such as automatic patching, encryption, and high availability, aligning with the stated requirements of minimal management and robust security.
- B. Incorrect.
A Bare Metal DB System requires you to manage scaling resources manually, which doesn't meet the requirement of minimal overhead and automatic handling of changes in demand. While a Bare Metal DB System can offer high performance, it lacks the autonomous features and auto-scaling capabilities needed here.
- C. Incorrect.
A VM DB System with manual patching and backups places additional administrative tasks on your team. This configuration does not provide auto-scaling for demand spikes. Although you can distribute the DB System across multiple Availability Domains for resilience, it still fails to deliver the simplified management sought.
- D. Incorrect.
While an Autonomous Database on Dedicated Infrastructure offers greater isolation and control, not enabling auto-scaling negates a key requirement. Your team would still have to manage capacity changes, making it a less suitable choice for an environment demanding automatic resource allocation.