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

The appropriate built-in Azure RBAC role is Monitoring Contributor . Microsoft defines this role for administrators who need to read monitoring information and create or modify monitoring configuration .

Monitoring Contributor includes the monitoring-read capabilities required to inspect metrics and diagnostic data and adds permissions needed to create or edit diagnostic settings, alert-related configurations, and monitoring resources. Microsoft also identifies creation of private monitoring dashboards as a supported use case for this role.

Monitoring Reader is insufficient because it is primarily a read-only monitoring role. It allows users to inspect monitoring data and settings but does not grant the required configuration-modification permissions. The general Reader role similarly lacks write capabilities. Owner would technically provide sufficient access but violates least privilege because it grants comprehensive resource-management permissions, including access-control authority far beyond monitoring.

Because the administrator's duties are specifically monitoring-oriented but require configuration changes, Monitoring Contributor supplies the correct functional scope without granting unrestricted ownership.

Study Guide reference: Secure Oracle AI Database@Azure — Azure RBAC, monitoring permissions, least privilege and operational administration

With the Default DNS option, Oracle automatically creates and manages the private DNS configuration associated with the Exadata VM Cluster. The generated database networking domain uses the oraclevcn.com suffix.

The Single Client Access Name (SCAN) listener and database-node FQDNs are registered within this Oracle-managed private DNS domain. OCI hosts the corresponding private DNS zone and, as part of the Oracle AI Database@Azure integration, the service replicates the required DNS records into a matching Azure Private DNS zone. Azure then links that private zone to the VNet hosting the Oracle database deployment, allowing Azure applications to resolve the Oracle database endpoints privately.

oraclecloud.com is broadly used for Oracle public cloud endpoints but is not the default private VCN suffix for the Exadata SCAN name. azure-database.net and oci-exadata.com are likewise not the default suffixes used by this Oracle-managed DNS architecture.

Therefore, D. oraclevcn.com is correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Exadata default DNS, SCAN and Azure Private DNS replication.

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

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.

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