1Z0-1084-25 OCI 2025 Developer Professional Practice Questions

While OCI does not have a dedicated state machine service like AWS Step Functions, the most robust way to build this long-running workflow using the available serverless components is with OCI Queue. Each step of the workflow can be a microservice (or function) that consumes a task from an input queue. Upon completion, it places a message in the next service's input queue. This pattern, often called queue-based workflow or choreography, is highly resilient, scalable, and suitable for long-running processes, as it decouples the services and avoids timeout limitations of services like OCI Functions.

OCI Logging automatically detects and parses log entries that are formatted as valid, single-line JSON objects. When it parses the JSON, it indexes the key-value pairs, allowing you to use them in search queries (e.g., where data.userId = '12345'). This practice is known as structured logging and is essential for effective log analysis in cloud environments.

OCI Service Mesh, which is built on open-source Istio, is specifically designed to provide these advanced capabilities. It injects sidecar proxies alongside each service to control all ingress and egress traffic, enabling features like fine-grained traffic shifting (for canary releases), fault injection (delaying or aborting requests for chaos testing), and automatic mTLS encryption between services, all without modifying the application code. Standard Kubernetes services and Ingress do not offer this level of control.

A Deployment is the standard and recommended Kubernetes object for managing stateless applications. It provides declarative updates to Pods and ReplicaSets. By defining the desired state in a Deployment manifest (e.g., 3 replicas, container image v1), you can simply update the manifest (e.g., change image to v2), and the Deployment controller will automatically manage a rolling update to the new version with zero downtime. While a Deployment uses a ReplicaSet underneath, you should manage the Deployment directly.

The statement is false. When a consumer retrieves a message from an OCI Queue, the message is not deleted. Instead, it becomes invisible for a configurable period called the 'visibility timeout'. This prevents other consumers from processing it. The consumer is responsible for explicitly deleting the message after it has been successfully processed. If the consumer fails to process and delete the message before the timeout expires, the message becomes visible again and can be picked up by another consumer, ensuring at-least-once delivery.

OpenTelemetry (OTel) is an open-source, vendor-neutral observability framework for instrumenting, generating, collecting, and exporting telemetry data (traces, metrics, logs). OCI APM has native support for the OpenTelemetry protocol (OTLP). By instrumenting applications with OpenTelemetry SDKs, developers can avoid vendor lock-in and send trace data to any compatible backend, including OCI APM.

A key advantage of microservices is that each service can be developed, tested, deployed, and scaled independently. This allows small, autonomous teams to work on different services in parallel, using different technology stacks if needed. It accelerates delivery because a change to one service does not require rebuilding and redeploying the entire application.

OCI Service Mesh is the correct choice as it is designed to manage, secure, and observe microservices. It provides features like mutual TLS (mTLS) for encrypting inter-service communication and sophisticated traffic management capabilities (e.g., traffic splitting for A/B testing) without requiring changes to the application code. A Network Load Balancer operates at L4 and doesn't manage internal service-to-service traffic rules. An API Gateway is for managing north-south traffic (from clients to the cluster), not east-west traffic (between services). Kubernetes Network Policies can restrict traffic but don't offer advanced routing or automatic mTLS.

OCI Streaming is the ideal service for this scenario. It supports a publish-subscribe model where a message published to a stream can be consumed by multiple independent consumer groups. Each consumer group maintains its own offset, allowing it to read all messages from the stream at its own pace. OCI Queue is designed for one-to-one message delivery, where a message is consumed by only one consumer. OCI Events Service is for reacting to state changes in OCI resources, not for custom application messaging. OCI Notifications is for simple fan-out to endpoints like email or PagerDuty but doesn't offer the persistent, replayable log semantics required by the consumer services.

Storing secrets in OCI Vault is the most secure and recommended approach. Vault provides a centralized, managed, and highly available service for secrets and encryption keys, with fine-grained access control via IAM policies.

Using an instance principal allows the application running on OKE worker nodes to securely authenticate with OCI Vault without needing to store long-lived credentials. This is a best practice for service-to-service authentication within OCI.