Oracle 1z0-1147 Practice Test Questions Answers

Oracle's current onboarding documentation explicitly states that customers purchasing through the Public Offer (Pay As You Go) must create a new OCI tenancy during onboarding.

The Public Offer is purchased directly in Azure Marketplace without negotiating a contract with Oracle Sales. Billing occurs through Azure, usage can count toward Microsoft Azure Consumption Commitment, and customers can start or stop consumption without a predetermined usage commitment. However, the trade-off relevant to this question is that an existing OCI tenancy cannot be linked to a Public Offer.

The Private Offer is different. Private Offer customers negotiate commercial terms with Oracle and can either link an eligible existing OCI tenancy or create a new OCI tenancy during onboarding.

Bring Your Own License affects Oracle Database software licensing economics rather than defining the Marketplace onboarding path. Universal Credits is likewise an OCI commercial construct and is not the Public/Private Oracle AI Database@Azure offer selection being tested.

Therefore, B is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Public Offer, Private Offer and OCI tenancy requirements.

===============

Oracle owns and operates the underlying Exadata infrastructure layer used by Oracle AI Database@Azure, even though that infrastructure is physically located in Microsoft Azure data centers. Consequently, Oracle performs infrastructure-level maintenance, patching, security updates, monitoring, and lifecycle operations.

Oracle-managed Exadata infrastructure components include the physical database-server hosts, storage servers, network fabric, hypervisor or virtualization infrastructure, firmware, management components, and control-plane systems. Microsoft supplies the Azure data-center environment and associated Azure platform capabilities, but Microsoft support engineers do not maintain Oracle's Exadata hardware/software stack.

The customer retains responsibility for customer-controlled portions of co-managed database environments, including database configuration and, depending on service and maintenance model, guest VM, Grid Infrastructure, database homes, and database software lifecycle activities. Oracle has also introduced optional Oracle-managed database software update capabilities for applicable newer Exadata services, but that does not change responsibility for the underlying infrastructure.

Therefore, C correctly identifies Oracle's Cloud Infrastructure operations organization.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — shared operational responsibility and Exadata infrastructure maintenance.

===============

Oracle Autonomous AI Database is specifically designed for workloads where elasticity and minimal administrative overhead are primary requirements. Oracle describes it as a fully autonomous, self-governing database service that handles provisioning, backups, patching, upgrading, performance management, and resource scaling without traditional database-administration effort.

For unpredictable workloads, compute auto scaling is particularly significant. When enabled, Autonomous AI Database can automatically consume additional CPU and I/O resources as workload demand rises without requiring an administrator to manually resize the database. Storage can likewise be scaled and can use separate auto-scaling functionality.

Exadata Database Service on Dedicated Infrastructure provides extremely high performance and consolidation capabilities but retains customer database-management responsibilities. Exascale Infrastructure improves Exadata's elastic infrastructure model but is still not equivalent to Autonomous Database's fully managed, self-governing operational model. Base Database Service similarly requires substantially more customer administration.

Therefore, a cloud-native application with volatile usage and a requirement for essentially zero database administration maps directly to Oracle Autonomous AI Database .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous AI Database, elastic scaling, automated management and serverless operations.

===============

Oracle Autonomous Container Database backup configuration includes an explicit backup-retention policy on termination . Administrators can select one of two supported behaviors: retain backups according to the normal configured backup-retention period, or retain them for 72 hours after termination and then delete them .

Oracle documentation identifies these options as RETAIN_PER_RETENTION_WINDOW and RETAIN_FOR_72_HOURS. The latter is the default in relevant API/Terraform configuration. Therefore, terminating an Autonomous Container Database does not inherently result in the immediate deletion of all automatic backups. Their post-termination lifetime is governed by the configured termination-retention policy.

Standard automatic backups are also not automatically converted into Long-Term Retention backups when the database is terminated. LTR backups have their own lifecycle and are explicitly excluded from the ordinary ACD termination-retention setting. No automatic export to Azure Blob Storage occurs as part of ACD termination.

Thus, B correctly reflects Oracle's documented post-termination backup behavior.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous Container Database automatic backups, termination and retention policy.

Oracle's Multicloud Architecture Framework emphasizes architectural considerations that arise because workloads, applications, data, identities, and operational responsibilities span multiple cloud providers. Two major areas are network latency/data movement and security, identity, and operations management .

Cross-cloud network latency can directly affect application response time, database performance, replication behavior, and transaction processing. Data movement can also introduce throughput constraints and cost considerations. Oracle therefore recommends workload placement and private connectivity strategies that minimize unnecessary cross-cloud distance and traffic.

Security and operations become similarly important because each cloud provider has its own IAM, monitoring, automation, and administrative models. Oracle recommends consistent identity and access policies, unified visibility, standardized automation, and common operational practices to avoid fragmented governance or management silos.

Hardware manufacturing origin and OCI hypervisor patch schedules do not represent the principal multicloud architectural design considerations described by the framework. Hypervisor maintenance is primarily a provider operational responsibility.

Therefore, B and D align directly with Oracle's documented multicloud design pillars.

Study Guide reference: Introduction to Multicloud — latency, data movement, Cloud Security, Cloud Operations, identity integration and operational standardization.

===============