A parking-citation microservice must pull work from OCI Queue. Which client approaches does Oracle document for Queue access?
Select an answer to reveal the explanation.
Short Explanation
Think of Queue as a counter that speaks two official languages: REST and STOMP. SDKs and the CLI ride those rails. Kafka clients belong on Streaming, not on Queue.
Full Explanation
OCI Queue is reached through the REST API described by OpenAPI and through the STOMP protocol. Oracle’s SDKs and the OCI CLI are built on those documented paths, so a parking-citation microservice that must pull work should use a REST or STOMP client—or an SDK/CLI wrapper over them—against the Queue endpoint. That design keeps produce and consume aligned with the service’s security model, IAM policies, and observability without inventing a third wire protocol.
Pointing a Kafka client library at the Queue endpoint fails by concept: Kafka-compatible produce/consume belongs to OCI Streaming, not Queue. Queue does not advertise itself as a Kafka broker, so Kafka framing, offsets, and consumer groups are the wrong abstraction. Treating AMQP 1.0 as the sole required Queue wire protocol also fails: Oracle documents REST and STOMP for Queue access, not a mandate that only AMQP brokers may talk to Queue. Routing every Queue message through OCI Streaming produce APIs first fails as well: Streaming is a separate append-only log product; Queue messages do not need to land in a stream before a worker can GetMessages and delete them.
Exam caveat: Domain 3 questions often bait you into swapping Queue and Streaming protocols—Kafka clients imply Streaming; Queue implies REST/STOMP. Operational check: from a staging tenancy, call GetMessages via the OCI CLI or an SDK REST client against a test channel and confirm IAM authorization and successful consume without configuring a Kafka bootstrap or AMQP broker.