Q: 8
As a DevOps engineer working on managing clusters on the OCI platform for your organization, which
statement is true about managing cluster add-ons in OCI OKE Cluster?
Options
Discussion
A The kicker is "essential" add-ons, which OCI OKE won't let you disable on first cluster creation. If the question was about optional add-ons instead, this would flip, but for essentials you have no choice. Pretty sure similar question comes up in practice for OKE clusters.
Option A since essential add-ons like CoreDNS can't be disabled during cluster creation in OKE. It's baked in for stability so OCI won't let you skip them. Pretty sure that's what the docs say too.
A . OCI OKE makes essential cluster add-ons mandatory, can't turn them off at creation. Pretty sure this matches what the official docs and practice exams say. If you want details, check the official guide for cluster creation steps.
Option A here. Essential add-ons like core DNS can't be disabled at cluster creation, they're required for cluster ops. Pretty sure that's what the docs highlight too. If anyone's seen different in recent OCI updates let me know.
I don't think it's C, since essential add-ons are required for OKE cluster creation and you can't disable them. A is correct here, pretty sure that's what the console enforces. Anyone see a reason to pick D instead?
A. saw exactly similar question in my exam and essentials couldn't be disabled at creation. 100% sure on this one.
A that's what came up in a similar question on my last practice. Essentials can't be skipped at creation.
A makes the most sense since those essential add-ons (like core DNS, kube-proxy) are required by OCI OKE for basic cluster ops. The docs say you can't turn them off at cluster creation, so you have to keep them enabled. Not 100% if anything changed recently, but that's how it's always worked imo. Let me know if anyone's seeing something different.
Makes sense, it's A here. Essentials can't be disabled at creation on OKE clusters.
A imo. Essentials like CoreDNS or networking add-ons can't be disabled when you create a new OKE cluster, it's enforced by OCI. I've seen similar phrasing in the official docs and practice sets. If you're in doubt, check the official guide for cluster creation steps.
Be respectful. No spam.
