Oracle 1z0-1084-26 Practice Exam Questions & Answers

OCI Vault is designed to securely store and manage secrets such as credentials and connection strings. By granting the function a resource principal and a dynamic group policy allowing access to the Vault secret, the function can retrieve the secret securely at runtime without ever exposing it in plaintext configuration or code. Storing it as a function config variable, hard-coding it, or using a public bucket all expose the secret or violate least-privilege security practices.

OCI API Gateway supports configuring authentication at the deployment level, including JWT-based authentication where the gateway validates the token's signature, issuer, audience, and expiration before forwarding the request to the backend. This offloads authentication from the backend services entirely. CORS policies control cross-origin browser behavior, logging policies only capture telemetry, and rate limiting controls traffic volume rather than validating identity tokens.

OCI Streaming is a Kafka-compatible, partitioned, append-only log service that allows multiple consumer groups to independently read and replay messages within a configurable retention period (up to 7 days). OCI Notifications is a publish-subscribe service for one-time delivery of alerts, not built for replay. OCI Queue is designed for point-to-point message delivery with visibility timeouts rather than multiple independent consumers replaying the same log. OCI Events reacts to resource state changes rather than serving as a general-purpose durable stream of application data.

OCI Resource Manager is Oracle's managed Terraform service that stores the state file remotely, provides plan and apply actions through the OCI console with approval workflows, and integrates with IAM policies to control who can create or manage stacks. OCI DevOps pipelines primarily orchestrate build/deploy stages and can call Resource Manager, but do not natively manage Terraform state. CLI scripting through Cloud Shell requires manual Terraform state handling, and instance configuration templates only address compute instance provisioning, not full infrastructure orchestration.

OCI Events rules support several action types including Notifications, Streaming, and directly invoking an OCI Function, so a Notifications topic is not required as an intermediary. If the function isn't triggering, likely causes include missing IAM policies granting the Events service permission to invoke the function, incorrect event type/condition filters, or the function not being in an ACTIVE state. The statement itself about direct Function invocation being supported is true.