Free 1Z0-1151-25 Practice Test

Tests

Identify provisioning interfaces for Oracle Database@Google Cloud

Difficulty

Easy

Key idea: Oracle Database@Google Cloud is ordered and provisioned from within the Google Cloud Console, which links into OCI Console workflows for Oracle-specific database management.

How to reach the answer

1. The question asks which interface provisions the Oracle-managed Exadata databases running in Google Cloud.
2. Oracle Database@Google Cloud is a co-engineered service, so its provisioning lives inside the Google Cloud Console rather than in a separate Oracle-only tool.
3. Oracle-specific settings such as licensing, backups and database configuration follow OCI workflows reached from within GCP.
4. Cloud Shell, Cloud SQL Admin and the Autonomous console are either generic CLIs or unrelated services, so C is the best fit.

Each option

• AIncorrect. Cloud Shell is a general-purpose command-line environment, not the dedicated provisioning interface for Oracle Database@Google Cloud.
• BIncorrect. There is no separate 'Oracle Autonomous Console' used to provision this service; Autonomous Database is one offering managed through the integrated console experience.
• CCorrect. Provisioning happens inside the GCP environment using OCI console workflows integrated with the Google Cloud Console.
• DIncorrect. Cloud SQL is Google's own managed MySQL/PostgreSQL/SQL Server service and has nothing to do with Oracle Exadata provisioning.

Common trap: Cloud SQL Admin sounds like the natural database admin tool in GCP, but Cloud SQL does not host Oracle Database@Google Cloud.

In practice: Architects plan Google Cloud project permissions and Marketplace onboarding first, because the Oracle database resources are then created from within the GCP console and managed in a linked OCI tenancy.

Remember: Oracle Database@Google Cloud is provisioned from the Google Cloud Console, using OCI workflows for Oracle-specific management, not from Cloud SQL or a standalone tool.

Official documentation: Oracle Database@Google Cloud

Tests

Recognize the management plane for Oracle Database@Google Cloud

Difficulty

Easy

Key idea: Day-to-day management of Oracle Database@Google Cloud starts in the Google Cloud Console, which ties into OCI Console functions for Oracle-specific operations.

How to reach the answer

1. The clue is 'from within the GCP environment', which points to a GCP-native console experience.
2. Oracle Database@Google Cloud integrates with Google IAM and projects, with OCI console capabilities reached from GCP for database operations.
3. SQL Developer is a client query tool, Azure DevOps belongs to another cloud, and Oracle VM Manager is a legacy on-premises virtualization tool.
4. Only B describes the integrated console model.

Each option

• AIncorrect. SQL Developer connects to databases for SQL work but does not provision or manage the cloud infrastructure.
• BCorrect. The Google Cloud Console with integrated OCI console workflows is the management interface for this service.
• CIncorrect. Azure DevOps is a Microsoft CI/CD toolset and is irrelevant to Google Cloud resource management.
• DIncorrect. Oracle VM Manager manages on-premises Oracle VM servers, not Exadata services in Google Cloud.

Common trap: Oracle SQL Developer is a familiar Oracle tool, so it can seem like the 'Oracle way' to manage the database, but it only works at the SQL layer.

In practice: Operations teams grant GCP IAM roles to DBAs so they can scale, back up and monitor Exadata databases without juggling a separate portal for every task.

Remember: Infrastructure-level management of Oracle Database@Google Cloud runs through the Google Cloud Console and its OCI integration; SQL clients are only for data access.

Official documentation: Oracle Database@Google Cloud

Tests

Understand Data Guard prerequisites in Oracle Database@Azure

Difficulty

Easy

Key idea: Data Guard needs a primary and a standby database that can reach each other over the network so redo can be shipped and applied.

How to reach the answer

1. Data Guard works by sending redo from a primary database to one or more standby databases.
2. That makes two database instances plus reliable connectivity between them the essential prerequisite.
3. Shared storage is a RAC concept, not a Data Guard one, and public IPs or NAT are neither required nor desirable.
4. Very old versions like 10g are not supported on Oracle Database@Azure, so C is the answer.

Each option

• AIncorrect. Oracle Database@Azure runs modern releases such as 19c and 23ai; 10g is neither required nor supported.
• BIncorrect. Data Guard keeps separate copies of the data at each site, so it does not rely on shared file storage.
• CCorrect. A primary and standby pair with network connectivity for redo transport is the core requirement.
• DIncorrect. Redo transport uses private networking such as peered VNets; public IPs and NAT are not prerequisites.

Common trap: Shared storage sounds like a high-availability requirement, but that belongs to RAC clustering, not to Data Guard replication.

In practice: For cross-region DR on Oracle Database@Azure, architects ensure the primary and standby VNets are connected and that routing and NSG rules allow the redo transport ports.

Remember: Data Guard requires two databases and private network connectivity between them, with no shared storage or public exposure.

Official documentation: Oracle Data Guard Concepts and Administration (19c)

Tests

Articulate the value proposition of Oracle Database@Azure

Difficulty

Easy

Key idea: Oracle Database@Azure places Oracle-managed Exadata inside Azure data centers with Azure-native identity, networking and billing integration.

How to reach the answer

1. The question asks what is gained compared with running purely in OCI or purely in Azure.
2. The key differentiator is Oracle Database services colocated in Azure, so apps get low latency through native VNet integration and Azure identity controls.
3. Licensing still follows BYOL or license-included models, so it does not reduce license counts.
4. AWS Lambda and eliminating VMs are unrelated, leaving B.

Each option

• AIncorrect. The service still uses VM clusters on Exadata, and application VMs remain normal; removing VMs is not the benefit.
• BCorrect. It delivers Oracle Database directly in Azure with integration into Azure networking and identity.
• CIncorrect. License requirements are not reduced; you use BYOL or license-included pricing as usual.
• DIncorrect. AWS Lambda is an Amazon service and has no role in Oracle Database@Azure.

Common trap: Option C appeals because multicloud offerings often advertise cost savings, but the savings come from MACC consumption and support, not fewer licenses.

In practice: Teams migrating Oracle-backed apps to Azure choose this service to keep Exadata performance and RAC while placing the database in the same region and network as Azure app tiers.

Remember: Oracle Database@Azure's value is Oracle database capabilities delivered natively within Azure networking and identity, with low latency to Azure apps.

Official documentation: Oracle Database@Azure

Tests

Plan network prerequisites for Oracle Database@Azure

Difficulty

Medium

Key idea: Exadata VM clusters attach to a delegated Azure subnet that must be sized correctly and reachable from application VNets, usually through VNet peering.

How to reach the answer

1. Oracle Database@Azure lands in an Azure VNet subnet delegated to Oracle, so the subnet must have enough addresses for the VM cluster nodes, VIPs and SCAN IPs.
2. Applications in other VNets reach the database through VNet peering, typically in a hub-and-spoke design.
3. FastConnect is an OCI-to-on-premises circuit and is not part of this deployment.
4. DNS forwarding can help with hybrid name resolution but is optional, so B and D are the answers.

Each option

• AIncorrect. DNS forwarding is an optional add-on for custom or hybrid resolution, not a deployment requirement.
• BCorrect. VNet peering connects application VNets to the VNet holding the Exadata delegated subnet.
• CIncorrect. FastConnect is OCI's dedicated private link and is not needed because the database runs inside Azure.
• DCorrect. The delegated subnet must have enough IP addresses for Exadata VM nodes, virtual IPs and SCAN listeners, plus future scaling.

Common trap: FastConnect looks required because OCI is involved, but the database runs inside Azure data centers, so Azure-native networking replaces it.

In practice: Network engineers reserve a properly sized CIDR for the Oracle delegated subnet early, because undersizing blocks VM cluster creation or later scale-out.

Remember: For Oracle Database@Azure, size the delegated subnet generously and peer application VNets to it; FastConnect does not apply.

Official documentation: Oracle Database@Azure

Tests

Explain architectural benefits of Oracle Database@Google Cloud

Difficulty

Easy

Key idea: Oracle Database@Google Cloud runs OCI-managed Exadata infrastructure inside Google data centers, so customers get the same Exadata service, tooling and performance as in OCI.

How to reach the answer

1. Recall the operating model: Oracle owns and operates the Exadata hardware and control plane, colocated in Google Cloud regions.
2. Ask what stays constant across clouds: the Exadata Database Service features, automation and support model.
3. Check which option is framed as an architectural advantage: consistency with Exadata on OCI.
4. Rule out options that misstate control (GCP-native), networking (public IPs) or licensing as the core architectural benefit.

Each option

• AIncorrect. The database service is still managed through OCI's control plane, so control is shared with OCI rather than fully GCP-native.
• BCorrect. The service delivers the same Exadata capabilities, tooling and operational model as Exadata Database Service on OCI.
• CIncorrect. Deployments use private connectivity within the customer's Google VPC; requiring only public IPs is false.
• DIncorrect. Marketplace purchasing and BYOL or license-included options are a commercial benefit, not the key architectural advantage asked about.

Common trap: Option D sounds attractive because Marketplace billing is heavily promoted, but it is a procurement feature, not an architectural one.

In practice: Teams already running Exadata on OCI or on-premises can move workloads next to GCP applications without retraining DBAs or rewriting automation.

Remember: Database@Google Cloud = OCI Exadata experience, physically inside Google Cloud.

Tests

Automate multicloud interconnect infrastructure with IaC

Difficulty

Easy

Key idea: OCI Resource Manager is the managed Terraform service that provisions networking components such as DRGs, FastConnect virtual circuits and route tables repeatably.

How to reach the answer

1. The clue is 'automate the creation' of infrastructure, which signals infrastructure as code.
2. Identify the OCI service that runs Terraform as a managed service: Resource Manager.
3. Confirm it can create interconnect pieces (DRG, VCN attachments, FastConnect, routing, security rules).
4. Eliminate services with unrelated purposes (API management, interactive shell, secrets).

Each option

• AIncorrect. API Gateway publishes and secures APIs and does not provision network infrastructure.
• BCorrect. Resource Manager runs Terraform stacks that create and manage interconnect resources consistently.
• CIncorrect. Cloud Shell is an interactive browser terminal; you could run scripts there, but it is not an automation service.
• DIncorrect. Vault stores keys and secrets, not infrastructure definitions.

Common trap: Cloud Shell includes Terraform and the CLI, so it can seem like an automation tool, but it is only a manual workspace without state management or job orchestration.

In practice: Architects build Resource Manager stacks that stand up DRGs and FastConnect or Azure/GCP interconnect circuits identically across dev, test and prod.

Remember: Automating OCI infrastructure means Resource Manager (managed Terraform).

Official documentation: Overview of Resource Manager

Tests

Configure authorization for federated identities in OCI

Difficulty

Easy

Key idea: Federation authenticates users externally, while OCI IAM policies grant permissions to the OCI groups those external groups are mapped to.

How to reach the answer

1. Separate authentication (handled by the external IdP via federation) from authorization (handled by OCI policies).
2. Group mapping links IdP groups to OCI groups.
3. Policies are written against groups ('Allow group X to ...'), so they grant federated users their permissions.
4. Options about federation rules, networking or database availability describe other mechanisms.

Each option

• AIncorrect. Federation trust and group mappings are configured on the identity provider/domain, not in IAM policies.
• BCorrect. Policies define what the mapped federated groups may do on which resources and compartments.
• CIncorrect. Network access is controlled by security lists, NSGs and routing, not IAM policies.
• DIncorrect. Database availability is an HA architecture concern, unrelated to IAM policies.

Common trap: Option A appeals because policies and federation are both IAM features, but policies only authorize; they do not define the federation trust.

In practice: When integrating Microsoft Entra ID with OCI for Database@Azure, you map Entra groups to OCI groups and write policies granting them database management rights.

Remember: IdP authenticates; OCI policies on mapped groups authorize.

Official documentation: How Policies Work

Tests

Use Resource Manager stacks for multi-compartment deployments

Difficulty

Easy

Key idea: A Resource Manager stack holds a Terraform configuration whose resources can target any compartments the executing user is authorized for, deployed in a single apply job.

How to reach the answer

1. The clue 'single deployment' across 'multiple compartments' points to IaC.
2. A stack's Terraform resources each specify a compartment_id, so one apply can span compartments.
3. Stacks track state and jobs for the whole deployment.
4. Other options are tools for shell access, nonexistent features, or log search.

Each option

• AIncorrect. Cloud Shell is a terminal, not a deployment construct that groups resources.
• BCorrect. A stack's Terraform configuration can create resources in multiple compartments in one job.
• CIncorrect. 'Autonomous Script' is not an OCI provisioning feature.
• DIncorrect. Logging search tools query logs and do not provision resources.

Common trap: Assuming a stack is bound to one compartment because the stack itself lives in a compartment; its resources can be placed elsewhere.

In practice: Landing zone templates use one stack to create network, security and workload compartments plus their resources together.

Remember: One stack can deploy resources to many compartments.

Official documentation: Overview of Resource Manager

Tests

Monitor Oracle Database@Azure health for high availability

Difficulty

Medium

Key idea: Database@Azure telemetry is visible both in Azure Monitor and in OCI Monitoring/Logging, giving infrastructure- and database-level health views.

How to reach the answer

1. Database@Azure is co-managed: Azure portal integration plus OCI control plane.
2. Oracle publishes database metrics and events to Azure Monitor for Azure-native observability.
3. OCI Monitoring and Logging provide detailed metrics for the underlying Exadata and databases.
4. Audit Vault focuses on audit/compliance and DevOps Insights is not a database health service, so both are eliminated.

Each option

• ACorrect. Azure Monitor receives Database@Azure metrics and supports alerts from the Azure side.
• BCorrect. OCI Monitoring and Logging expose Exadata and database health metrics in the OCI console.
• CIncorrect. Audit Vault collects audit data for security and compliance, not HA health monitoring.
• DIncorrect. Azure DevOps insights cover development pipelines, not database runtime health.

Common trap: Audit Vault sounds like an Oracle database monitoring tool, but it tracks user activity for compliance, not availability.

In practice: Operations teams set Azure Monitor alerts for application owners while DBAs use OCI metrics to watch Data Guard and Exadata health.

Remember: Database@Azure health: Azure Monitor plus OCI Monitoring/Logging.