1Z0-1084-25 Sample Questions & Answers

Multi-stage builds are a Docker feature designed for this exact purpose. They allow you to use multiple FROM instructions in a single Dockerfile. Each FROM instruction begins a new build stage. You can selectively copy artifacts from one stage to another, leaving behind everything you don't want in the final image, such as build tools and intermediate files.

OCI Functions have a maximum execution timeout of 300 seconds (5 minutes). A task that takes 10 minutes will always fail. The correct architectural pattern is to have the initial HTTP-triggered function accept the request, place the task details onto a queue (like OCI Queue), and return an immediate '202 Accepted' response. A separate, asynchronously triggered function (or another worker process) would then consume from the queue to perform the long-running task.

The correct command is docker push. To push to OCIR, the image must first be tagged with the fully qualified repository name, which follows the format .ocir.io/ / :. Assuming the image was correctly tagged (e.g., docker tag my-app:v1.1 iad.ocir.io/mytenancy/my-app:v1.1), this docker push command will upload it to the specified OCIR repository. iad is the region key for us-ashburn-1.

OCI Events Service is designed for this exact use case. It allows you to create rules that respond to state changes in OCI resources. By creating a rule that filters for the 'Object - Create' event in the specified compartment and bucket, and setting the action to invoke an OCI Function, you create a fully managed, event-driven, and efficient pipeline without any custom polling or intermediate services.

The kubectl logs command fetches the logs from the standard output and standard error streams of the container(s) within the pod. For a CrashLoopBackOff error, this is the most direct way to see the application's error messages or stack traces that are causing it to exit prematurely. kubectl describe is useful for viewing events and configuration, but the application's specific error will be in its logs.

The Circuit Breaker pattern is a resiliency mechanism that monitors for failures. When the number of failures reaches a certain threshold, the circuit breaker 'trips' or 'opens', and for a configured duration, all further calls to that service fail immediately without being attempted. After the timeout, the circuit breaker allows a limited number of test requests to pass through. If those succeed, it 'closes' the circuit and resumes normal operation. This prevents a client from repeatedly trying to call a failing service, which can exhaust resources and cause cascading failures.

The primary goal of contract testing is to verify that two separate systems (like a consumer and a provider microservice) are compatible and can communicate with each other. It captures the interactions in a 'contract' that is tested against each service independently. This allows teams to detect integration issues early in their respective CI/CD pipelines without needing to deploy and run a full, complex end-to-end integration test environment.

For custom authentication logic, such as validating a key from a non-standard header, the correct approach is to use a custom authorizer function. This involves creating an OCI Function that receives request context (including headers), performs the validation logic against a database or vault, and returns a JSON response indicating whether the request is authenticated and authorized. This provides maximum flexibility for non-standard authentication schemes.

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.