Core OCI Services practice questions

Worked examples for Core OCI Services

1. Question 1

   A company hosts an application server in a private subnet behind a NAT gateway. Partners on the public internet now need to open HTTPS connections directly to that server. Why does the existing NAT gateway not satisfy this new requirement?

   1. A. A NAT gateway only allows connections initiated from inside the VCN; it never accepts connections initiated from the internet.Correct answer

      Correct: NAT is one-way by design — it translates outbound-initiated flows and their return traffic, and offers no way for an external host to initiate a session inward.

   2. B. A NAT gateway accepts inbound connections but only on ports below 1024, so HTTPS on port 443 is rejected.

      Invents a port restriction. The limitation is directional, not port-based, and 443 is in fact below 1024's exclusion logic only in this fabricated rule.

   3. C. A NAT gateway supports inbound traffic only after a stateless security list rule is added to the private subnet.

      Assumes a security rule can change routing behaviour. Security lists filter traffic that the gateway can already carry; they cannot make a NAT gateway accept inbound-initiated sessions.

   4. D. A NAT gateway forwards inbound traffic only when the private subnet is also attached to a Dynamic Routing Gateway.

      Confuses on-premises connectivity with internet ingress; a DRG carries private VPN/FastConnect traffic and does not enable inbound internet flows through a NAT gateway.

   Explanation

   NAT is inherently unidirectional: the gateway maps outbound-initiated connections from private resources and permits only the corresponding return packets, so no host on the internet can start a session toward the private instance (Networking overview). Accepting partner-initiated HTTPS requires a public-facing entry point such as a public load balancer, or moving the workload to a public subnet with an internet gateway. Port thresholds, stateless security rules, and DRG attachments all describe unrelated mechanisms and none of them makes NAT bidirectional.

2. Question 2

   Which TWO statements accurately describe the difference between Autonomous Database on serverless deployment and Autonomous Database on dedicated Exadata infrastructure? (Choose two.)

   1. A. With serverless deployment, Oracle manages all aspects of the infrastructure and the database runs on shared Exadata infrastructure.Correct answer

      Serverless is the simplest form of Autonomous Database: Oracle owns and operates the underlying shared Exadata infrastructure and the customer works only with the database.

   2. B. Dedicated deployment gives the customer a private database cloud on Exadata infrastructure that is not shared with other tenants.Correct answer

      Dedicated Autonomous Database provisions Exadata infrastructure exclusively for one customer, giving greater isolation and customer control over policies such as maintenance scheduling.

   3. C. Only the dedicated deployment provides self-driving, self-securing, and self-repairing automation; serverless requires manual tuning and patching.

      Claims automation is exclusive to dedicated; both deployment choices are Autonomous Database and both are self-driving, self-securing, and self-repairing.

   4. D. Serverless deployment supports only the data warehouse workload type, while dedicated supports only transaction processing.

      Invents a workload restriction per deployment model; workload type and deployment model are independent choices.

   5. E. Dedicated deployment removes Oracle Database compatibility, requiring applications to be rewritten for a proprietary API.

      Fabricates an API change; both deployment models run Oracle Database and existing Oracle applications and tools connect normally.

   Explanation

   Autonomous Database offers two deployment choices that differ in infrastructure isolation and control: serverless runs on Exadata infrastructure that Oracle owns, operates, and shares across tenants, while dedicated provisions Exadata infrastructure exclusively for one customer as a private database cloud. Automation is a property of Autonomous Database itself, so self-driving, self-securing, and self-repairing behaviour applies to both deployments rather than only to dedicated. Workload type — transaction processing or data warehouse — is chosen independently of the deployment model, and neither deployment alters Oracle Database compatibility for existing applications.

3. Question 3

   A company is migrating a licensed database engine that must run directly on physical hardware with no hypervisor layer between the operating system and the server, and it requires the entire machine's compute capacity. Which OCI Compute instance type best fits this requirement?

   1. A. A virtual machine instance on a flexible shape sized to the largest available OCPU count

      Assumes that making a VM large enough is equivalent to physical hardware. A VM always runs on a hypervisor and shares the underlying physical host, which is exactly what the requirement excludes.

   2. B. A Container Instance configured with the maximum OCPU and memory allocation

      Confuses a serverless container runtime with a server. Container Instances run containerized workloads on Oracle-managed infrastructure; the customer never gets an OS on physical hardware.

   3. C. A bare metal instanceCorrect answer

      Correct: a bare metal instance gives the customer a dedicated physical server with no hypervisor, so the OS runs directly on the hardware and the tenant gets the whole machine's capacity and strongest isolation.

   4. D. An instance pool of virtual machines fronted by a load balancer

      Treats horizontal scale-out as a substitute for single-machine physical access. Pooling VMs adds copies of virtualized instances; it does not remove the hypervisor or give access to the physical server.

   Explanation

   OCI Compute offers bare metal instances, which are dedicated physical servers with no hypervisor, giving the tenant the full machine, the strongest isolation, and direct hardware access — the fit for licensed engines that must see physical hardware. Sizing a virtual machine larger does not change the fact that it is virtualized and shares a host, and clustering multiple VMs behind a load balancer only multiplies virtualized capacity. Container Instances are a serverless way to run containers on Oracle-managed infrastructure, so they never expose an operating system running on physical hardware.

4. Question 4

   An organization runs a mission-critical Oracle Database estate that requires the highest available Oracle Database performance and scale, consolidating many databases onto engineered infrastructure with scale-out storage designed specifically for Oracle Database. Which OCI database offering should be selected?

   1. A. MySQL HeatWave Database Service, scaled to its largest shape

      Picks a MySQL engine for an Oracle Database estate; shape size does not change the fact that HeatWave does not run Oracle Database.

   2. B. Base Database Service on a single virtual machine

      Underprovisions the requirement: a single VM offers neither engineered Exadata infrastructure nor the consolidation scale described.

   3. C. Exadata Database ServiceCorrect answer

      Exadata Database Service runs Oracle Database on Oracle Exadata engineered infrastructure, the offering targeted at the highest Oracle Database performance, availability, and large-scale consolidation.

   4. D. Autonomous Database serverless

      Serverless Autonomous runs on shared Exadata infrastructure managed by Oracle; it does not give the organization the dedicated engineered estate for consolidating its own database fleet.

   Explanation

   Exadata Database Service delivers Oracle Database on Oracle's Exadata engineered systems, which combine database servers with scale-out storage built for Oracle Database, and is the offering positioned for the most demanding performance, availability, and consolidation requirements. A single Base Database Service VM cannot supply that infrastructure or scale. MySQL HeatWave is a different database engine entirely. Serverless Autonomous Database is fully abstracted and shared, so it does not provide a dedicated engineered estate for consolidating an existing Oracle fleet.

5. Question 5

   An operations team wants to see CPU utilization trends for their compute instances and be alerted automatically when utilization stays above a threshold. Which OCI service category owns this responsibility, and which service delivers it?

   1. A. Integration — OCI Integration, which connects applications and automates business processes between them.

      Misconception: confusing integration with monitoring. Integration services connect applications and orchestrate data flows between them; they do not collect resource metrics or raise threshold alarms.

   2. B. Observability and management — OCI Monitoring, which collects metrics from resources and triggers alarms on defined thresholds.Correct answer

      Correct. OCI Monitoring sits in the observability and management category and is the service that queries emitted metrics such as CPU utilization and fires alarms when a metric crosses a configured threshold.

   3. C. Networking — OCI Load Balancer, which distributes incoming traffic across a set of backend servers.

      Misconception: assuming a traffic-distribution service is also the metrics and alerting service. A load balancer performs health checks purely to route traffic; it does not provide general metric history or user-defined alarms.

   4. D. Identity and security — OCI Identity and Access Management, which controls who can access which resources.

      Misconception: conflating access governance with operational telemetry. IAM authenticates and authorizes principals against resources; it has no role in gathering performance metrics or alerting on them.

   Explanation

   Metric collection and threshold-based alerting belong to OCI's observability and management category, where the Monitoring service queries metrics emitted by resources and evaluates alarms against them. Integration services move data and coordinate processes between applications rather than instrument infrastructure. A load balancer's health checks serve only its own routing decisions and are not a general telemetry or alerting facility. Access-control services decide permissions and never measure resource performance.

6. Question 6

   A SaaS provider runs its application on MySQL. It now wants to run analytical queries against the same operational data in near real time, and specifically wants to avoid exporting data to a separate analytics database. Which OCI service directly addresses this requirement?

   1. A. MySQL HeatWaveCorrect answer

      Correct. MySQL HeatWave is OCI's managed MySQL service with an integrated in-memory query accelerator, so transactional and analytic queries run against the same MySQL database without moving data to a separate analytics system.

   2. B. Autonomous Data Warehouse

      Misconception that analytics always means a separate data warehouse. ADW is an Oracle Database service, so using it would require exactly the data movement and re-platforming the provider wants to avoid.

   3. C. Autonomous Transaction Processing

      Misconception that Autonomous Database can serve as a drop-in MySQL replacement. ATP is an Oracle Database workload type, not a MySQL-compatible engine.

   4. D. Base Database Service

      Misconception that Base Database Service is a general-purpose managed database for any engine. It provides customer-managed Oracle Database systems, not MySQL, and offers no in-memory analytics accelerator.

   Explanation

   MySQL HeatWave is OCI's fully managed MySQL service augmented with an in-memory accelerator, letting transaction processing and analytics run on one MySQL database and removing the need for an extract step into a separate analytic system. The Autonomous Database workload types are Oracle Database services and would require migrating the application off MySQL. Base Database Service likewise provides Oracle Database systems and adds nothing to accelerate MySQL analytics.

7. Question 7

   Which TWO workloads are the best fit for Autonomous Data Warehouse rather than another OCI database service?

   1. A. A payment authorization service handling thousands of short read/write transactions per second with strict latency limits.

      Puts an OLTP workload on the analytics-tuned Autonomous Database type; this pattern belongs on the transaction processing workload type.

   2. B. A business-intelligence dashboard running complex aggregate queries across several years of historical data.Correct answer

      Correct. Long-running aggregate queries over large historical datasets are the analytic pattern the data warehousing workload type is tuned for.

   3. C. An application whose vendor requires root access to the database host to install a certified agent.

      Misconception that Autonomous Database exposes the host OS. Host-level access requires a customer-managed offering such as Base Database Service.

   4. D. A departmental data mart that consolidates data loaded from several source systems for ad-hoc analysis.Correct answer

      Correct. Consolidating loaded data for ad-hoc analytical querying is a classic data warehouse and data mart use case, served by the data warehousing workload type with no infrastructure management.

   5. E. An application that must connect using the MySQL wire protocol.

      Confuses Autonomous Database with a MySQL-compatible service. MySQL clients require the managed MySQL offering, not an Oracle Database service.

   Explanation

   Autonomous Data Warehouse is the Autonomous Database workload type built for analytics — dashboards, reporting, and data marts that load data and then run complex, scan-heavy aggregate queries — with Oracle automating tuning and maintenance. High-concurrency short transactions belong to the transaction processing workload type instead. Requirements for host operating-system access point to a customer-managed Oracle DB system, and MySQL protocol compatibility points to the managed MySQL service, neither of which Autonomous Data Warehouse provides.

8. Question 8

   A team runs a latency-sensitive UDP-based game service and needs the backend servers to observe the original client source IP address. Which OCI service best fits this workload?

   1. A. Network Load BalancerCorrect answer

      Correct: the Network Load Balancer is a Layer-4 (TCP/UDP/ICMP) load balancer built for ultra-low latency that can preserve the client source IP to the backends.

   2. B. Load Balancer with an HTTP listener

      Applies a Layer-7 HTTP service to a UDP workload; the Load Balancer proxies HTTP/HTTPS (and TCP) and does not serve UDP traffic.

   3. C. A Local Peering Gateway between the client VCN and the server VCN

      Confuses VCN-to-VCN connectivity with load distribution; an LPG connects networks and does not balance traffic across servers.

   4. D. A service gateway fronting the backend fleet

      Confuses private access to Oracle services with a customer-facing traffic distribution endpoint.

   Explanation

   The Network Load Balancer operates at Layer 4 over TCP, UDP, and ICMP, is optimized for very low latency and high throughput, and can pass the client's original source IP through to backends — precisely what a UDP game service needs (Network Load Balancer overview). The Load Balancer is an application-layer proxy for HTTP/HTTPS and TCP and does not handle UDP, while a Local Peering Gateway and a service gateway are connectivity components that perform no load distribution at all.