1z0-1147 Dumps with Practice Exam Questions Answers

Oracle Zero Downtime Migration is Oracle Maximum Availability Architecture's recommended orchestration framework for moving Oracle databases while minimizing production interruption. For physical online migration , ZDM uses Oracle Data Guard. The target database is instantiated as a physical standby, redo generated on the source is transported and applied to the target, and ZDM coordinates the eventual switchover. Oracle documentation for Oracle Database@Azure specifically states that physical online migration uses direct data transfer, Restore From Service, and Oracle Data Guard to keep source and target synchronized.

For logical online migration , the underlying synchronization technology is Oracle GoldenGate. Oracle Data Pump provides the initial logical export/import, after which GoldenGate captures ongoing source transactions and applies them to the target until cutover. This workflow can also accommodate scenarios involving different database versions or platforms.

Oracle Sharding is an application/data-distribution architecture rather than ZDM's replication mechanism. Far Sync is a Data Guard component for specialized zero-data-loss configurations but is not the primary technology identified for ZDM migration orchestration.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM physical online migration, logical online migration, Data Guard, GoldenGate, Data Pump.

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

Oracle's current service-availability matrix states that Oracle Exadata Database Service on Dedicated Infrastructure is eligible for Private Offer only . It is not available through the Public Offer/Pay As You Go purchasing model.

Therefore, if an organization originally onboarded Oracle AI Database@Azure using the Public Offer and subsequently requires Dedicated Exadata Infrastructure, the commercial relationship must be changed by engaging Oracle Sales and obtaining the appropriate Private Offer .

A delegated-subnet service-limit increase affects networking capacity and does not enable a database service that is excluded by the selected Marketplace offer. BYOL can reduce Oracle Database licensing charges where eligible, but licensing model and Marketplace service eligibility are separate issues. Changing an Autonomous Database workload type is completely unrelated to Exadata hardware procurement.

Oracle's current service table also shows why the confusion can arise: Exadata Database Service on Exascale Infrastructure is available through both Public and Private Offers, whereas Exadata Database Service on Dedicated Infrastructure remains Private Offer only.

Therefore, A is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — offer eligibility and Dedicated Infrastructure purchasing.

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

Oracle AI Database@Azure has specific client-subnet IP consumption requirements that must be considered during capacity planning. For the delegated client subnet, 13 IP addresses are reserved for networking services regardless of the number of VM Clusters deployed in that subnet .

Microsoft's Oracle AI Database@Azure networking documentation defines these 13 addresses as the first four addresses, the ninth through sixteenth addresses, and the final address of the subnet. Applied to 10.0.0.0/24, the reserved ranges are therefore 10.0.0.0–10.0.0.3, 10.0.0.8–10.0.0.15, and 10.0.0.255.

These platform reservations must be counted in addition to addresses needed for VM nodes and SCAN addresses. For example, every VM consumes multiple client-network addresses, and each VM Cluster requires SCAN addresses. Failing to account for the reserved block can therefore result in insufficient address capacity even when a subnet initially appears large enough.

Only option B precisely represents the documented reserved address positions.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet planning, client subnet sizing, reserved networking-service IP addresses and Exadata VM Cluster capacity.

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

The uploaded study set keys D , because it attempts to preserve data inside the same geographical region while obtaining a separate fault domain.

There is, however, an important current-documentation qualification. Oracle AI Database@Azure maps an OCI Availability Domain to an Azure Availability Zone , and Oracle MAA documentation describes local Data Guard standby deployments on another Exadata infrastructure in the same or a separate Azure Availability Zone . Oracle's cross-zone Data Guard implementation explicitly requires primary and standby Oracle AI Database@Azure deployments in two supported Azure AZs.

Therefore, option D is valid only if the second OCI Availability Domain corresponds to another supported Oracle AI Database@Azure Azure AZ. If the premise is literally that Oracle AI Database@Azure is available in only one Azure AZ and cross-region replication is prohibited, current Oracle documentation does not provide a second independent Oracle AI Database@Azure site simply by selecting an unmapped OCI AD.

For the uploaded question's intended key, the answer remains D , but the architecture should be treated with this deployment-availability condition.

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

For a cross-region Autonomous Data Guard standby , Oracle specifies a maximum possible data-loss objective of approximately 1 minute . Accordingly, the intended Recovery Point Objective is one minute.

Cross-region protection differs from a local Autonomous Data Guard standby because geographical distance makes fully synchronous zero-data-loss transport impractical for normal cross-region operation. Oracle therefore uses an asynchronous protection model that provides a bounded RPO while maintaining acceptable database performance.

A useful distinction is between RPO and RTO. RPO measures potential data loss, whereas RTO measures how long restoration of service is targeted to take. Oracle's current Autonomous AI Database Serverless SLO documentation continues to specify a 1-minute cross-region RPO . Current documentation has improved the cross-region RTO target to less than 10 minutes ; older material cited approximately 15 minutes. That RTO evolution does not affect the answer to this question because only RPO is being tested.

Zero data loss therefore applies to different protection scenarios, while five and fifteen minutes do not represent the documented cross-region RPO.

Study Guide reference: HA and DR — Autonomous Data Guard local and cross-region recovery objectives.

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