1Z0-997-25 exam dumps: 175 free OCI 2025 Architect Professional practice questions

Correct answers: A, C

• A. Correct.

  Option 1 is correct. Oracle Service Mesh (or a similar service mesh solution) enables fine-grained control over service-to-service communication, enforces zero-trust security models, and provides traffic metrics and policies for microservices. This is a recommended practice for securing and managing complex microservices architectures on OCI.

• B. Incorrect.

  Option 2 is incorrect. Exposing microservices directly to the internet via ephemeral IP addresses increases the attack surface and complicates service discovery and security. A better design is to secure internal traffic within a private subnet and use managed services like API Gateway or a service mesh for external access and inter-service communication.

• C. Correct.

  Option 3 is correct. Oracle API Gateway allows you to decouple external clients from your internal microservices by providing a single entry point for requests, handling security, authentication, request routing, and traffic throttling. This is a recommended pattern for cloud-native applications.

• D. Incorrect.

  Option 4 is incorrect. Hardcoding credentials in container images is an insecure practice. Instead, you should store and manage secrets externally, such as using OCI Vault or Kubernetes Secrets, to ensure credentials remain protected and easily rotatable.

Correct answers: A, C

• A. Correct.

  Option 1: Correct. Using OCI Container Registry (OCIR) is a best practice for storing, versioning, and scanning container images. It integrates seamlessly with OKE, improving security and simplifying deployment flows.

• B. Incorrect.

  Option 2: Incorrect. Storing container images on a single Compute instance and manually syncing is neither scalable nor aligned with cloud-native best practices. OCIR provides secure, centralized storage.

• C. Correct.

  Option 3: Correct. OCI DevOps Pipelines offer a managed CI/CD service that integrates with OKE. This automates build, test, and deploy stages, streamlining the continuous delivery process.

• D. Incorrect.

  Option 4: Incorrect. Ephemeral local storage is lost when containers exit or nodes are replaced. For persistent data, OCI provides persistent volumes or block storage. It's not recommended to rely on ephemeral local storage for data retention in production.

Correct answer: B

• A. Incorrect.

  A) Incorrect: Placing all services on a single VM instance and scaling by adjusting the instance shape is manually intensive and does not leverage cloud-native capabilities such as Kubernetes-based auto-scaling. This approach increases operational overhead and does not offer the high availability you typically need for production traffic spikes.

• B. Correct.

  B) Correct: Using Oracle Container Engine for Kubernetes (OKE) with the Horizontal Pod Autoscaler (HPA) is a recommended cloud-native approach, allowing automatic scaling of microservices. Storing application state in an external data store such as an Autonomous Database ensures stateless service containers, making them more resilient and easier to scale up and down as traffic demands change.

• C. Incorrect.

  C) Incorrect: While a hybrid or on-premises approach can sometimes be valid, hosting the Kubernetes cluster on-premises for a cloud-native solution negates many auto-scaling benefits and can introduce latency issues. Also, you lose some of OCI� fully managed capabilities that reduce operational overhead.

• D. Incorrect.

  D) Incorrect: Relying solely on local ephemeral storage for stateful services is not aligned with cloud-native best practices. If containers restart, any state stored locally is lost, which can lead to data inconsistency. Furthermore, manual scaling does not efficiently handle sudden traffic surges.

Correct answers: A, B

• A. Correct.

  Correct. Oracle Container Engine for Kubernetes (OKE) supports automatic horizontal pod autoscaling, enabling microservices to dynamically scale based on demand. This design minimizes idle resource costs because when traffic is low, the number of pods can decrease, and when traffic spikes, additional pods are provisioned automatically.

• B. Correct.

  Correct. Oracle Functions is a serverless platform that automatically spins up execution environments only when needed. It� ideal for short-lived or event-driven tasks, such as order validation, because you pay only for the actual time your function runs, reducing overhead during idle periods.

• C. Incorrect.

  Incorrect. Oracle Exadata Cloud Service is intended for high-performance database workloads, not transient microservices or event-driven tasks. Using Exadata for ephemeral workloads is both cost-inefficient and operationally complex for the scenario described.

• D. Incorrect.

  Incorrect. Deploying all microservices on a single Oracle Compute instance with manual scaling can lead to excessive costs when the instance sits idle. Moreover, manual scaling is error-prone, inefficient for handling sudden traffic spikes, and does not provide the flexibility of autonomous or serverless scaling.

Correct answers: A, C

• A. Correct.

  Option 1 is correct. Oracle Functions can leverage OCI Events Service to automatically invoke serverless functions when new messages arrive in OCI Streaming. This design pattern is essential for event-driven architectures, allowing functions to run code only when needed and scale seamlessly with incoming events.

• B. Incorrect.

  Option 2 is incorrect. Manually resizing fixed-shape nodes on Oracle Container Engine for Kubernetes provides scalability but increases operational overhead and does not fully leverage OCI's serverless offerings. This approach can be used but does not align with a purely event-driven, serverless design.

• C. Correct.

  Option 3 is correct. OCI Streaming provides a scalable and durable messaging backbone, enabling microservices to process data asynchronously. By triggering serverless functions for on-demand transformations, you achieve both elasticity and loose coupling among services.

• D. Incorrect.

  Option 4 is incorrect. Oracle Functions is a fully managed service running on OCI infrastructure�you do not deploy a custom VM for it. This choice does not reflect the serverless nature of Oracle Functions, which abstracts away the operating system management.

• E. Incorrect.

  Option 5 is incorrect. While integrating Oracle Functions with an API Gateway is a common pattern for microservices, standalone usage behind an API Gateway does not inherently address high-throughput event ingestion or real-time data processing. The key requirement in the scenario is near real-time event-driven architecture, which is best met by pairing functions with OCI Streaming and Events.

Correct answers: A, B

• A. Correct.

  Option 1 is correct. Horizontal Pod Autoscaling (HPA) in OKE allows automatically scaling up and down based on workload demand. This ensures real-time services can handle dynamic traffic levels without manual intervention. This is a recommended OCI best practice for cloud-native architectures seeking to minimize operational overhead.

• B. Correct.

  Option 2 is correct. Oracle Functions is a serverless platform ideal for short-running, event-driven tasks. Using OCI Events to trigger Functions offloads asynchronous workflows from containerized environments, reducing overhead and ensuring cost efficiency. Reference: 'Using Oracle Functions with Events' in the OCI documentation.

• C. Incorrect.

  Option 3 is incorrect. Storing persistent state in container file systems creates complexity for scaling and reliability. In Kubernetes, container file systems are ephemeral and not meant to hold stateful data. Instead, using Autonomous Database or persistent storage volumes is the recommended approach.

• D. Incorrect.

  Option 4 is incorrect. Manual node scaling adds unnecessary operational burden. Although it can temporarily reduce cost if workloads are predictable, it fails to handle sudden traffic spikes effectively and is not aligned with cloud-native best practices.

Correct answers: A, C

• A. Correct.

  Correct. Spreading node pools across multiple Availability Domains improves high availability and resilience, reducing downtime risks if one domain experiences an outage.

• B. Incorrect.

  Incorrect. Using a single partition for Oracle Streaming can create a bottleneck. Multiple partitions should be used for parallel processing and higher throughput.

• C. Correct.

  Correct. The Horizontal Pod Autoscaler automatically increases or decreases pod counts based on defined metrics, helping to handle traffic spikes without manual intervention.

• D. Incorrect.

  Incorrect. Oracle Functions is a serverless offering that runs separately from OKE. Functions should not be deployed as a sidecar container; this is not a supported or recommended design pattern in OCI.

Correct answer: A

• A. Correct.

  Correct. Using OCI DevOps for your build pipeline ensures integrated builds, tests, and deployments. The pipeline can automatically push container images to Oracle Container Registry, and OKE supports rolling deployment strategies for minimal downtime. This approach also facilitates quick rollbacks if a deployment fails.

• B. Incorrect.

  Incorrect. While a private on-premises registry can be used, manually updating OKE deployments with scripts increases operational overhead and risk of errors. This approach doesn't leverage OCI DevOps features that automate and streamline the CI/CD process.

• C. Incorrect.

  Incorrect. Blue-green deployments are a valid strategy in some scenarios, but spinning up entirely new clusters on-demand for every release is often more costly and operationally complex than rolling updates within a single OKE cluster.

• D. Incorrect.

  Incorrect. Combining all microservices into one large container goes against microservices best practices, making updates more disruptive. Manually restarting all pods also increases downtime and operational errors.

Correct answer: B

• A. Incorrect.

  Option 1 is incorrect because manually managing Docker containers on standalone Compute instances without a container orchestration platform complicates scalability and CI/CD integration. Storing images in an external registry also introduces additional security and network considerations that OCI can handle internally with OCIR.

• B. Correct.

  Option 2 is correct. Oracle Container Engine for Kubernetes (OKE) provides a managed Kubernetes environment, which is ideal for scaling microservices. OCI DevOps Build and Deployment pipeline automates code integration and deployment. Using OCIR for storing container images ensures security and performance within the OCI environment, and mutual TLS enables secure inter-service communication.

• C. Incorrect.

  Option 3 is incorrect because Oracle Functions is serverless and is best suited for event-driven, short-running tasks rather than a full microservices e-commerce platform. Also, using OCI Block Storage for container images is less efficient compared to a dedicated container registry like OCIR. Manual pushes do not align with DevOps automation best practices.

• D. Incorrect.

  Option 4 is incorrect because running microservices on a database system equipped with Docker containers is not a recommended design. It couples compute and database resources, reducing flexibility. Storing container images in Object Storage and using third-party CI/CD without OCI integration overlooks OCI� secure and scalable DevOps capabilities.

Correct answers: A, C

• A. Correct.

  Option 1 is correct because using OCI DevOps pipelines, integrating with a version control system, and storing images in OCIR is a recommended best practice for continuous integration and deployment. Rolling updates in OKE minimize downtime and streamline the release process.

• B. Incorrect.

  Option 2 is incorrect because embedding credentials directly in Dockerfiles is insecure and not aligned with best practices. It exposes secrets when images are built and stored in registries.

• C. Correct.

  Option 3 is correct as storing sensitive information in Oracle Vault and referencing them through Kubernetes secrets improves security and adheres to principle of least privilege. OCI supports this pattern for microservices running in OKE.

• D. Incorrect.

  Option 4 is incorrect because generally, you do not need a separate OKE cluster for each microservice. A single OKE cluster can effectively isolate microservices while simplifying operational overhead through namespaces and network policies.

• E. Incorrect.

  Option 5 is incorrect because bundling all microservices in a single image negates the advantages of modular deployments. It complicates updates and scaling, going against the main benefits of microservices architectures.