Curious about Actual Oracle Cloud (1Z0-997-23) Exam Questions?

Correct : A

Option A is correct because using Autonomous Transaction Processing with shared Exadata infrastructure is the most suitable option for running seasonal workloads in Oracle Cloud Infrastructure. Autonomous Transaction Processing is a fully managed, serverless, and elastic database service that can scale up or down automatically based on the workload demand. It also supports stopping and starting the database to save costs when it is not in use. It runs on Exadata infrastructure, which provides high performance, availability, and security for transactional and mixed workloads12.

Option B is incorrect because using Oracle Cloud Infrastructure Exadata DB Systems is not optimal for running seasonal workloads in Oracle Cloud Infrastructure. Exadata DB Systems are dedicated, high-performance database systems that can run multiple databases with different shapes and versions. However, they are not serverless or elastic, and they do not support stopping and starting the database. They are more suitable for mission-critical and steady-state workloads that require consistent performance and availability3 .

Option C is incorrect because using Oracle Cloud Infrastructure Virtual Machine DB Systems is not optimal for running seasonal workloads in Oracle Cloud Infrastructure. Virtual Machine DB Systems are flexible and cost-effective database systems that can run single-node or RAC databases with different shapes and versions. However, they are not serverless or elastic, and they do not support stopping and starting the database. They are more suitable for development, testing, or production workloads that require moderate performance and availability .

Option D is incorrect because using Oracle Cloud Infrastructure Bare Metal DB Systems is not optimal for running seasonal workloads in Oracle Cloud Infrastructure. Bare Metal DB Systems are high-performance database systems that run single-node databases with locally attached NVMe storage. However, they are not serverless or elastic, and they do not support stopping and starting the database. They are more suitable for high-performance, latency-sensitive, specialized, or traditional workloads that require full control over the entire cloud stack .