Oracle Updated 1z0-1084-26 Exam Questions and Answers by lia

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.

Oracle ' s current OCI Streaming limits specify that each stream partition supports a total data write rate of 1 MB per second. Partition count is therefore a fundamental capacity-planning parameter for producer workloads. If an application is expected to produce more than 1 MB per second, the stream must contain enough partitions to distribute the required ingress throughput appropriately. Oracle ' s partitioning guidance likewise states that expected throughput should be calculated before stream creation because each partition is limited to the 1 MB-per-second write rate. The 2 MB figure is not the documented write limit, while 4 MB and 8 MB exceed the per-partition ingress capacity. Therefore, the maximum write throughput represented by the available choices is 1 MB per second.

OKE Workload Identity is anenhanced-cluster capability. Oracle ' s current Kubernetes Engine documentation explicitly lists workload identity as supported by Enhanced clusters and not supported by Basic clusters. Workload Identity enables IAM policies to authorize individual Kubernetes workloads according to attributes such as cluster, namespace, and service account, avoiding broader permissions inherited from worker-node instance principals. Basic clusters support standard Kubernetes and OKE functionality but exclude enhanced capabilities including Workload Identity, virtual nodes, self-managed nodes, and advanced cluster add-on management. “Dedicated cluster” and “Autonomous cluster” are not the OKE cluster types used for this feature classification. Therefore, an application architecture requiring OKE Workload Identity must use an Enhanced cluster, making option A correct.