1Z0-1085-23 · Question #182
A banking platform has been re-designed to a microservices based architecture using Docker containers for deployment. Which service can you use to deploy containers on Oracle Cloud Infrastructure…
The correct answer is A. Container Engine for Kubernetes (OKE). See the full explanation below for the reasoning.
Question
A banking platform has been re-designed to a microservices based architecture using Docker containers for deployment. Which service can you use to deploy containers on Oracle Cloud Infrastructure (OCI)?
Options
- AContainer Engine for Kubernetes (OKE)
- BStreaming Service
- CAPI Gateway
- DFile Storage Service
How the community answered
(21 responses)- A76% (16)
- B14% (3)
- C5% (1)
- D5% (1)
Community Discussion
4The correct answer is A, Container Engine for Kubernetes (OKE). OKE is OCI's managed Kubernetes service, and Kubernetes is purpose-built for orchestrating containerized workloads at scale, which is exactly what a microservices re-architecture needs. You get a card-worthy distinction here: OKE handles the container lifecycle, scheduling, scaling, and networking between pods, so it is the natural fit when the question mentions Docker containers and microservices deployment together. The other three options are distractors that serve entirely different functions, Streaming handles event pipelines, API Gateway manages HTTP request routing, and File Storage is a shared NFS solution, none of which deploy or run containers.
Good breakdown, though worth adding that when they mention "auto-scaling" in the question stem, that is the extra nudge toward OKE since it integrates directly with the Kubernetes Horizontal Pod Autoscaler out of the box.
Saw this one on my actual 1Z0-1085-23 sitting last month and honestly my senior had just walked me through OKE the week before so it clicked right away, Container Engine for Kubernetes is exactly what OCI gives you for running containerized workloads at scale. The other options threw me for a second since I kept second-guessing myself on API Gateway, but once I remembered that Streaming and File Storage have nothing to do with running containers, and API Gateway is just for routing, OKE was the only one that made sense.
OKE is the right pick, but do you know why OCI chose Kubernetes over plain Docker Swarm here?