Explanation

The two statements that are NOT valid regarding the Oracle Cloud Infrastructure (OCI) Streaming service are: A stream can be configured with either a public or a private endpoint with support for customer managed encryption keys. This statement is not valid because the OCI Streaming service currently supports only private endpoints. Customer managed encryption keys are not currently supported for OCI Streaming. OCI Streaming can support up to 2,000 requests per second to each partition. This statement is not valid because the throughput of a stream is not defined by the partition in terms of requests per second. The throughput of a stream is defined in terms of data input and output rates. Each partition provides 1 MB/sec data input and 2 MB/sec data output, but it does not correspond to a specific number of requests per second. The other statements are valid: OCI Streaming stores all data for 24 hours by default, but that can be extended up to 7 days. Although OCI Streaming automatically encrypts all data while in transit, it is the developer ' s responsibility to encrypt data at rest, if needed.

Option D is invalid because OCI Streaming imposes a maximum request/message payload size of approximately1 MiB, not 10 MB. Oracle ' s current Streaming documentation also verifies the remaining statements. Stream retention can be configured between 24 hours and seven days. Cursors are temporary consumption pointers and expire five minutes after being returned by the service. Private endpoints can be configured at the stream-pool level using a private subnet in a VCN, keeping producer and consumer traffic from traversing the public internet. These limits affect application architecture directly: payloads larger than the Streaming request limit normally need to be chunked or stored externally with only a reference carried in the message. Therefore, D is the only invalid statement.

The logconfig.json file is a configuration file that specifies how the Unified Monitoring Agent collects and uploads custom logs to the OCI Logging service2. The logconfig.json file contains an array of objects, each representing a custom log configuration2. Each custom log configuration object has the following fields2:

logGroupObjectId: The OCID of the log group where the custom log is stored.

logObjectId: The OCID of the custom log.

paths: An array of paths to files or directories containing the custom logs.

src: A regular expression that matches the files containing the custom logs.

parser: A parser definition that specifies how to parse the custom logs. If the logconfig.json file has incorrect or missing OCID for the custom log in the logobjectId field, or incorrect or missing OCID for the custom log group in the logGroupObjectId field, then the Unified Monitoring Agent will not be able to upload the custom logs to the OCI Logging service2. Therefore, these are potential reasons for logs from the Meshifyd application not showing up in the OCI Logging service. Verified References: Unified Monitoring Agent Configuration File

Explanation

The correct answer is: Invoke from the Docker CLI.Explanation: Executing a function deployed in Oracle Functions is typically done using the following options: Invoke from the Fn Project CLI: The Fn Project CLI provides a command-line interface specifically designed for interacting with Oracle Functions. You can use commands like fn invoke to invoke a function. Trigger by an event in the Oracle Cloud Infrastructure (OCI) Events service: You can configure events in OCI to trigger your function based on various criteria, such as object storage events, resource state changes, or scheduled events. Invoke from the OCI CLI: The OCI CLI (Command Line Interface) allows you to interact with various services in Oracle Cloud Infrastructure, including Oracle Functions. You can use the fn invoke command to invoke a function. Send signed HTTP requests to the function ' s invoke endpoint: Oracle Functions provides an HTTP endpoint that can be used to invoke functions. You can send signed HTTP requests to this endpoint using tools or programming languages that support making HTTP requests. On the other hand, invoking a function deployed in Oracle Functions using the Docker CLI is not a valid option. The Docker CLI is primarily used for managing Docker containers and images, and it does not provide a direct mechanism for invoking functions in Oracle Functions.

OCI Queue exposes separate IAM resource types specifically to enforce producer/consumer separation. Oracle documents queue-push for producers and queue-pull for consumers. The policy Allow dynamic-group payment-producer-dg to use queue-push in compartment prod-payment-compartment grants only QUEUE_PRODUCE, which covers the PutMessages API operation. It does not grant GetMessages, DeleteMessage, queue configuration reads, or queue administration. By comparison, use queues is broader because the general queues resource type includes read, update, produce, and consume capabilities. queue-pull provides consumer permissions rather than producer permissions, and manage queue-push is not the correct permission model for this specialized resource type. Therefore, A precisely implements least-privilege publishing for the producer microservice.

Statement D is NOT valid. Oracle ' s cloud application architecture guidance explicitly describes integration testing as validating interactions and data flow between components, modules, and services. In a cloud-native architecture, those interactions commonly occur through network-based APIs, service endpoints, databases, and messaging systems. Oracle recommends test environments that resemble production rather than restricting integration testing to isolated developer workstations. Unit testing does focus on individual units of code and typically isolates dependencies. API mocking can emulate unavailable dependent services, while performance testing evaluates responsiveness, scalability, and stability under varying workloads such as load and stress conditions. Therefore, the claim that integration testing is exclusively local and does not validate network communication contradicts the actual purpose of integration testing.

Oracle separates secret-management operations from retrieval of secret contents. The current OCI CLI command for retrieving a secret bundle is oci secrets secret-bundle get --secret-id < secret_id > . If no specific version, stage, or version name is supplied, Oracle returns the bundle associated with the secret version marked CURRENT. The secrets data-plane command retrieves the actual secret bundle, including its encoded content and version properties. The alternative command paths shown in A, C, and D do not represent the documented OCI CLI operation for obtaining secret contents. Oracle ' s current Secrets Management documentation provides the same command directly when describing how applications and administrators retrieve a secret ' s contents. Therefore, option B is the exact verified command.

The Docker daemon, implemented as the dockerd background process, runs continuously on a Docker host and performs the server-side container-management operations requested through the Docker API. It manages container execution, images, storage drivers and volumes, and networking. The Docker client is the command interface that sends requests to that daemon; it does not itself manage container lifecycles. A Docker registry such as OCIR stores and distributes images remotely, while Docker Compose describes and coordinates multi-container application configurations. Oracle ' s Linux container documentation explicitly refers to the Docker Engine daemon and its dockerd process, and Oracle Functions troubleshooting likewise distinguishes the local Docker client/daemon from the remote registry. Therefore, the persistent management component described in the question is the Docker Daemon.

Explanation

The two main reasons to choose a serverless architecture are: Automatic horizontal scaling: Serverless architectures allow for automatic scaling of resources based on demand. The infrastructure automatically provisions and scales resources as needed, ensuring that applications can handle varying workloads efficiently. This eliminates the need for manual scaling and optimizes resource utilization. Reduced operational cost: Serverless architectures follow a pay-per-use model, where you are billed only for the actual execution time and resources consumed by your functions. This leads to cost savings as you don ' t have to pay for idle resources. Additionally, serverless architectures remove the need for managing and maintaining servers, reducing operational overhead and associated costs.Explanation: No need for integration testing: Integration testing is still necessary in serverless architectures to ensure that functions integrate correctly with other components and services. Serverless functions can interact with various event sources, databases, and APIs, and testing is required to verify the integration points. Improved in-function state management: Serverless architectures typically encourage stateless functions that operate on short-lived requests or events. While there are mechanisms to manage state within a function, serverless architectures are designed to be stateless by default, promoting scalability and fault tolerance. Easier to run long-running operations: Serverless functions are generally designed for short-lived operations rather than long-running tasks. If you have a requirement for long-running operations, a serverless architecture may not be the ideal choice, as it has execution time limits and may not provide the necessary resources for extended execution.

Oracle provides a dedicated logging-search OCI CLI command group for querying indexed log content. The documented syntax is oci logging-search search-logs, with --search-query, --time-start, and --time-end as the principal parameters required to define the Logging Query Language expression and search interval. The ordinary oci logging command group is used for administration of logs and log groups rather than searching their contents. logging-query is not a valid top-level OCI CLI service group, and --query-string is not the documented search parameter. Therefore, option B exactly matches Oracle ' s current CLI command reference for submitting a programmatic log search across custom or service logs.