Oracle Updated 1z0-1147 Exam Questions and Answers by georgina

Under the default managed-DNS model, Oracle derives the private Oracle domain from normalized VNet and delegated-subnet naming components. In the source scenario, the production and DR resource names share the same leading characters, causing both sites to derive the same oraclevcn.com private DNS namespace.

The practical resolution is therefore to alter the naming inputs before deployment so the generated DNS labels are unique. The uploaded question set specifies that the relevant generated tokens use the first 11 alphanumeric characters , so either the DR VNet or delegated subnet must be renamed such that the derived prefix differs from the active environment.

The Host Domain Name field associated with default managed DNS is system-generated rather than freely editable. Adding another DNS resolver does not eliminate the underlying duplicate private-zone namespace, and DNS views cannot reliably correct a collision created at resource provisioning.

Therefore, D resolves the root cause while retaining Oracle-managed DNS.

Study Guide reference: Configure Oracle AI Database@Azure Networking — default DNS, oraclevcn.com, VNet/subnet DNS derivation and DR naming design.

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

Oracle AI Database@Azure supports two broad TDE master-key management approaches: Oracle-managed keys and customer-managed keys .

With the default Oracle-managed model, the TDE master encryption key is generated and stored in an Oracle Wallet within the database environment. Oracle manages key generation, storage, rotation, backup, and restoration activities associated with this model.

For customer-controlled key management, Oracle supports several external key stores. For Exadata Database Service on Dedicated Infrastructure, these include Azure Key Vault , OCI Vault, and Oracle Key Vault. Azure Key Vault integration is particularly useful for organizations that want their database encryption-key governance aligned with existing Azure key-management, auditing, and separation-of-duties practices.

AWS KMS and Google Cloud KMS are not native key-management choices for an Oracle AI Database@Azure Exadata deployment.

Therefore, the two correct selections from this answer set are A and D .

Study Guide reference: Secure Oracle AI Database@Azure — Transparent Data Encryption, Oracle Wallet, customer-managed keys and Azure Key Vault.

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

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 AI Database@Azure integrates its operational telemetry with Azure Monitor diagnostic settings so organizations can apply existing Azure observability, compliance, and SIEM architectures to Oracle database infrastructure.

Three standard destinations are relevant here. An Azure Log Analytics workspace receives telemetry for centralized querying, dashboarding, alerting, and Kusto Query Language analysis. An Azure Storage account can archive logs or metrics for retention, compliance, or later processing. Azure Event Hubs provides a streaming destination for forwarding telemetry to SIEM products, custom consumers, event-processing pipelines, or other downstream platforms.

Oracle's Oracle AI Database@Azure monitoring documentation specifically lists Log Analytics Workspace, Storage Account, and Event Hub among the available Azure Monitor diagnostic-routing destinations. Oracle Enterprise Manager can monitor Oracle environments but is not an Azure Monitor diagnostic-settings destination. OCI Object Storage is likewise not selected directly as a destination from the Azure diagnostic-settings workflow. Azure SQL Database is a database service rather than a supported diagnostic sink.

Therefore, the three correct selections are A, C, and D .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — monitoring, Azure diagnostic settings, Log Analytics, Storage accounts and Event Hubs.

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