Pass the Oracle Cloud Infrastructure 1z0-1147 Questions and answers with Dumpstech

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's reference architecture for multi-region Oracle Database@Azure disaster recovery explicitly states that no subnet is required in the Hub VCN to enable transit routing .

The Hub VCN serves primarily as a routing construct connecting gateways and route-table attachments. DRGs, Local Peering Gateways, Remote Peering Connections, and VCN route tables provide the required network forwarding between the Oracle Database@Azure Child Site VCNs and remote regions. Because the hub does not need to host compute instances or network virtual appliances for this gateway-based transit model, it does not require a workload subnet.

This has an additional design benefit: the hub VCN can use a comparatively small CIDR range because there is no requirement to reserve substantial address space for servers or VNICs.

A public subnet and Internet Gateway are unnecessary because Data Guard traffic should traverse private cloud networking. Likewise, dedicated /24 transit-appliance subnets or per-availability-domain private subnets are not mandatory for the gateway-based topology.

Therefore, D is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — cross-region Data Guard, OCI Hub VCN and transit routing.

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

The -eval option invokes the evaluation workflow of Oracle Zero Downtime Migration rather than executing the production migration. Oracle specifically directs administrators to use ZDMCLI migrate database ... -eval to evaluate the migration process, including prerequisite checks, source/target connectivity verification, configuration validation, and applicable pre-migration assessment phases.

The resulting job is an evaluation job rather than a migration job that performs database movement. This distinction is reflected throughout ZDM command handling: ZDM can query evaluation jobs separately from actual migration jobs, and the evaluation workflow is intended to identify prerequisite or configuration failures before production data movement begins.

The option does not create a mock standby or execute a simulated Data Guard switchover. It also does not begin an offline migration and stop before the copy phase. CPAT may participate in migration-readiness assessment depending on ZDM version and command options, but -eval is not an installation command for CPAT.

Consequently, A correctly represents the effect: an EVAL-type workflow performs migration prechecks and validation without executing the actual migration.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM CLI, evaluation mode, migration validation and prechecks.

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

The purchase process creates an Azure-managed resource group in the background to host the OracleSubscription resource used for Oracle AI Database@Azure billing and subscription integration. Microsoft specifically documents a known issue in which Azure Policy can block this operation.

The system-created managed resource group must initially be located in EastUS , must conform to the provider-defined naming requirement, and is initially created without tags . Consequently, an enterprise policy that allows only West Europe or denies untagged resource groups prevents the OracleSubscription resource from being created. The correct remediation is to exempt the applicable managed resource group from those blocking policies during the purchase process. Microsoft recommends identifying the blocking assignment in the Azure activity log and creating an appropriate, preferably time-bound, Azure Policy exemption.

Administrators cannot solve the problem by manually creating their own resource group in West Europe because this is a provider-managed resource. Billing-address changes likewise do not change the resource provider's required deployment location, and OCI commercial-model changes do not remove the Azure OracleSubscription requirement.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — private offer purchase, OracleSubscription resource, Azure prerequisites and policy considerations.

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

The correct staging medium is an Azure Files NFS share . Oracle's ZDM documentation for Autonomous AI Database Serverless on Oracle Database@Azure explicitly supports Azure Files as an NFS file-share source for Data Pump migration staging.

In the logical migration workflow, the NFS share is made accessible to the source database and attached to the Autonomous AI Database target. Data Pump export files can therefore be written to and read from the shared location without being staged in OCI storage. Oracle specifically documents mounting Azure Files NFSv4.x and exposing the path through a database directory for Data Pump operations.

OCI Object Storage and OCI File Storage would place the staging data within OCI, violating the explicit requirement that dump files remain in the Microsoft Azure subscription. Azure Blob Storage can be accessed by Autonomous Database through DBMS_CLOUD for supported object-storage workflows, but the standard ZDM NFS-based Data Pump staging mechanism described in this question uses a mounted filesystem rather than a direct Blob REST API.

Therefore, C is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM, Autonomous AI Database Serverless, Data Pump and Azure Files NFS.

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

Oracle documents a specific 404 NotAuthorizedOrNotFound condition that can occur during Exadata VM Cluster creation when the selected private DNS zone does not already contain tags. Oracle then attempts to generate the default OCI oracle-tags, but the multicloud service principal must have permission to use the associated tag namespace.

The required policy statement is:

Allow any user to use tag-namespaces in tenancy where request.principal.type = 'multicloudlink'

Oracle's current troubleshooting guidance also requires the companion permission:

Allow any user to manage tag-defaults in tenancy where request.principal.type = 'multicloudlink'

The crucial detail is that the provisioning operation executes under the multicloudlink principal type , not an ordinary administrator group or a principal with request.user.id='multicloud'. Merely granting inspect permission is insufficient because the service must actually apply the tag namespace/defaults.

Thus, among the supplied options, C is the required policy statement.

Study Guide reference: Secure Oracle AI Database@Azure — OCI IAM, MulticloudLink service principal and tagging permissions.

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

Among the choices presented, Oracle Exadata Database Service on Dedicated Infrastructure and Oracle Autonomous AI Database are both native Oracle AI Database@Azure database services designed to run on Oracle-optimized database infrastructure located inside Azure data centers. Exadata Database Service provides customer-managed Oracle Database environments on purpose-built Exadata hardware, with RAC, Data Guard, elastic compute, and high-performance storage capabilities. Autonomous AI Database provides a fully managed database model in which Oracle automates provisioning, patching, tuning, backup operations, and resource scaling.

Oracle's current service portfolio has expanded further and now also includes Exadata Database Service on Exascale Infrastructure, Base Database Service, Autonomous AI Database on Dedicated Exadata Infrastructure, GoldenGate, and Autonomous Recovery Service. However, those services are not alternatives in this question. Oracle NoSQL Database Cloud Service is not one of the listed Oracle AI Database@Azure database offerings, while a generic Oracle Database Standard Edition VM running on Azure IaaS is not equivalent to a native Oracle AI Database@Azure service.

Therefore, B and C are correct. Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — supported database services and optimized Oracle infrastructure.

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

The appropriate architecture is Microsoft Entra ID-to-OCI SAML federation combined with group synchronization/mapping .

SAML provides the authentication component. Administrators authenticate using corporate Microsoft Entra ID identities and obtain federated access to the associated OCI Identity Domain. Oracle's onboarding procedure creates the SAML trust by exchanging metadata between Microsoft Entra ID and OCI.

The provisioning side then maps assigned users and groups from the Microsoft Entra enterprise application into OCI through the configured identity integration. This allows corporate group membership to drive the user's Oracle-side authorization model instead of requiring administrators to create and maintain separate OCI identities individually.

Azure RBAC governs Azure resources but does not by itself create the required OCI IAM group relationships for OCI Console administration. Azure Key Vault controls cryptographic keys and secrets rather than identity federation, while manually creating OCI users directly contradicts the automated identity-lifecycle requirement.

Therefore, A provides both SSO and centralized enterprise identity/group management.

Study Guide reference: Secure Oracle AI Database@Azure — SAML federation, user/group synchronization and OCI IAM.

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

For Oracle AI Database@Azure's documented Azure-to-OCI federation architecture, Microsoft Entra ID functions as the enterprise identity provider. Oracle's reference architecture explicitly states that Microsoft Entra ID provides federated identity and access management for Oracle AI Database@Azure.

The OCI IAM Identity Domain remains an essential component because it is the Oracle-side service provider and identity domain that trusts the Microsoft Entra identity provider. However, when the question asks which platform provides the federated corporate identity in the Azure-integrated architecture, the answer is Microsoft Entra ID.

Oracle's onboarding instructions configure an Oracle Cloud Infrastructure Console enterprise application in Entra ID and then configure the OCI identity domain with Microsoft Entra ID as its SAML identity provider. Administrators can subsequently use their corporate Entra credentials for SSO into OCI when Oracle-native management tasks require it.

AD FS represents an older on-premises Microsoft federation service, while Okta is a third-party identity platform rather than the natively documented Azure integration.

Therefore, A is correct.

Study Guide reference: Secure Oracle AI Database@Azure — Entra ID federation, OCI IAM Identity Domains and SSO.

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

The invalid managed backup destination is the physical Zero Data Loss Recovery Appliance (ZDLRA) .

Oracle AI Database@Azure currently provides two primary managed automatic backup destinations for Exadata databases: Oracle Database Autonomous Recovery Service and OCI Object Storage . Oracle recommends Autonomous Recovery Service because it provides database-aware incremental-forever protection, policy-based retention, recoverability validation, optional real-time redo protection, and retention-lock capabilities.

Long-Term Retention is a supported capability of Recovery Service and allows selected backups to be preserved for extended compliance periods. It therefore represents a valid managed backup lifecycle option, even though technically it is a Recovery Service feature rather than an independent storage system.

The Zero Data Loss Recovery Appliance is a physical Oracle engineered system primarily used in customer data centers and appropriate Cloud@Customer architectures. Autonomous Recovery Service incorporates technologies derived from the Recovery Appliance but is delivered as a managed cloud service; these two should not be confused.

Therefore, the answer to the "NOT valid" question is B .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata automatic backups, Object Storage and Autonomous Recovery Service.

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