A corporation is building a web application to allow its customers to schedule service requests...

Oracle 1z0-931-25 Question Answer

A corporation is building a web application to allow its customers to schedule service requests online. There is also a need to run operational reports at times during non-peak hours. The architecture team is debating whether such reports should be run on the OLTP database or in a separate data mart. The DBA Manager does not want to add any more admin responsibility to the team and is looking for a database option that’s low to zero maintenance, but meets their strict performance requirements as well. Which Oracle Cloud Infrastructure database service is appropriate for this scenario?

ATP using 'tpurgent' and 'high' TNS services to separate connection types

Since the application needs to be highly available, it should be deployed on a Kubernetes Cluster

It is best to build a separate data warehouse, and move the OLTP data on a nightly basis

ADW since operational reporting is a higher priority in this scenario

Explanation:

The scenario requires a low-maintenance, high-performance database for an OLTP web application with occasional reporting. The correct answer is:

ATP using 'tpurgent' and 'high' TNS services to separate connection types (A):Autonomous Transaction Processing (ATP) is ideal here. It’s a fully managed database optimized for OLTP workloads (e.g., scheduling service requests) with zero maintenance overhead—Oracle handles patching, backups, and tuning. ATP supports multiple connection services:

'tpurgent':Prioritizes low-latency, time-critical transactions (e.g., customer scheduling requests), ensuring fast response times for the web app.

'high':Suited for high-concurrency or reporting queries, allowing operational reports to run during non-peak hours without impacting the OLTP workload.By using these predefined services, the architecture separates transactional and reporting workloads within the same database, meeting performance needs without additional administration. For example, the web app connects via tpurgent for real-time updates, while a reporting tool uses high for batch queries at night, leveraging ATP’s auto-scaling if needed.

The incorrect options are:

Since the application needs to be highly available, it should be deployed on a Kubernetes Cluster (B):This misinterprets the question—it’s about the database service,not the application deployment. Kubernetes is for container orchestration, not a database solution, and adds complexity counter to the low-maintenance goal.

It is best to build a separate data warehouse, and move the OLTP data on a nightly basis (C):While a separate Autonomous Data Warehouse (ADW) could handle reporting, it requires data movement (e.g., via ETL), increasing admin effort and complexity, which the DBA Manager wants to avoid. ATP can handle both workloads with proper service separation.

ADW since operational reporting is a higher priority in this scenario (D):ADW is optimized for analytics, not OLTP. The web app’s transactional needs are primary, with reporting secondary and occasional, making ATP more suitable.

ATP’s self-managing nature and service flexibility make it the best fit.

[Reference:Oracle Cloud Infrastructure Documentation -ATP Overview, ]

Oracle 1z0-931-25 View All Questions