1z0-1147 Dumps with Practice Exam Questions Answers

An Oracle AI Database@Azure delegated subnet remains part of the customer's Azure VNet and can use supported Azure networking controls. Two fundamental controls are Network Security Groups (NSGs) and Azure route tables containing User-Defined Routes .

An NSG performs traffic filtering by applying inbound and outbound security rules based on criteria such as source, destination, protocol, and port. This allows organizations to enforce database-access policies at the Azure network layer. Route tables provide forwarding control, allowing traffic to be directed through Azure Firewall, an NVA, a virtual network gateway, or other supported next-hop architecture.

Oracle's delegated-subnet design documentation explicitly states that because the delegated subnet belongs to the customer's VNet, it can leverage Azure networking capabilities including NSGs and routing tables . This enables private application-to-database communication while retaining enterprise routing and security controls.

Azure Load Balancer backend pools and Application Gateway ingress controllers are application/load-balancing constructs and are not the two subnet-associated controls identified for this Oracle database networking requirement.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet design, NSGs, Azure route tables, UDRs and traffic controls.

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

The standard Oracle Autonomous AI Database Serverless resource-allocation interface permits the administrator to configure the base compute allocation up to 512 ECPUs using the ECPU slider. This value represents the configured base ECPU count for a single database instance rather than the potential temporary compute consumption obtainable through compute auto scaling.

Oracle distinguishes configured ECPUs from auto-scaled usage. For eligible Autonomous AI Database configurations, compute auto scaling can allow the database to consume additional processing capacity above the configured base according to workload demand. For example, a database configured with 512 ECPUs may be capable of consuming substantially more effective processing capacity when auto scaling is enabled, subject to the service and licensing model.

The 1024-ECPU option therefore does not represent the normal single-instance slider ceiling addressed by this question. The 256- and 128-ECPU values are valid intermediate configurations but are below the maximum.

Consequently, A. 512 ECPUs is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous AI Database Serverless provisioning, ECPU configuration and compute scaling.

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

Oracle Exadata Database Service on Exascale Infrastructure uses the Elastic Compute Processing Unit (ECPU) resource model. During initial VM Cluster provisioning, Oracle requires a minimum of 8 ECPUs enabled per VM .

The distinction between the initial minimum and subsequent scaling increments is important. After the VM Cluster exists, enabled compute capacity is adjusted in increments of 4 ECPUs . Therefore, 4 ECPUs represents the scaling granularity, not the minimum provisionable starting configuration. Oracle also allows enabled ECPUs to be reduced to zero after provisioning when administrators need to temporarily shut down the VMs and suspend enabled-ECPU usage billing, but zero cannot be used as the initial active configuration.

Current Oracle documentation defines the supported total ECPU allocation per VM within the applicable Exascale service limits and explicitly states that the provisioned value must be a multiple of four.

Consequently, neither 1 nor 4 meets the initial provisioning baseline, while 16 is valid but exceeds the minimum. The correct answer is A. 8 ECPUs .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exascale VM Cluster sizing and ECPU configuration.

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

Oracle's current network guidance defines two important delegated-subnet constraints. First, each Azure VNet can contain a maximum of one Oracle AI Database@Azure delegated subnet . Second, a single delegated subnet can support multiple VM Clusters , provided IP capacity and availability-zone constraints are satisfied.

Oracle clarifies that multiple VM Clusters from the same Exadata Infrastructure can share a delegated subnet. VM Clusters belonging to different Exadata Infrastructure resources can also share one when those infrastructure resources reside in the same availability zone .

However, Exadata Infrastructure resources located in different availability zones cannot share the same delegated subnet. Oracle identifies such a configuration as producing a suboptimal network path and requires separate delegated networking for cross-zone deployments.

The delegated subnet also uses Azure private address space; it is not required to use—and should not be designed around—a public IPv4 CIDR range.

Therefore, A and C are correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated-subnet limits, VM Cluster placement and IP addressing.

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

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.

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