1Z0-1072-25 Question 198
Single answerYour company runs a financial reporting application on Oracle Cloud Infrastructure that experiences heavy I/O operations at month-end. You currently use the Balanced performance tier for your 2 TB block volumes. To manage costs but still meet peak performance demands, which approach is recommended?
- A
Clone the volume and attach both volumes to the compute instance during peak I/O periods to achieve double the performance without changing tiers.
- B
Dynamically switch to a higher performance tier during peak usage and revert to the Balanced tier when peak demand subsides.
- C
Create a new volume in a different region on the Ultra High Performance tier and replicate data using block volume backups before every month-end event.
- D
Migrate data to object storage during non-peak periods and move it back to block storage during peak periods.
Show answer and explanation
Correct answer: B
Explanation
For predictable peak workloads, Oracle Cloud Infrastructure Block Volumes supports changing between performance tiers in real time without needing to re-provision or migrate data. The recommended approach is to use a higher performance tier during heavy I/O and revert to a lower tier afterward for cost savings. Refer to the OCI Block Volume documentation for details on switching tiers and associated cost considerations.
- A. Incorrect.
Incorrect: Cloning the volume does not combine I/O performance. Cloning makes a point-in-time copy but does not share or aggregate I/O throughput in a way that doubles performance.
- B. Correct.
Correct: OCI Block Volumes allows changing performance tiers in-place. Scaling up during peaks optimizes performance and reverting to a lower tier reduces costs when the workload is lighter.
- C. Incorrect.
Incorrect: Creating a new volume in a different region and replicating data would be more complex, time-consuming, and potentially more expensive. It's not the most efficient method for short, predictable peaks.
- D. Incorrect.
Incorrect: Migrating data to object storage does not address high I/O performance needs for block-based workloads. Object storage is primarily for unstructured data and isn't a solution for rapid IOPS during peak.