Q: 1
You are a DevOps project administrator. You are creating Oracle Cloud Infrastructure (OCI) Identity and Access Management (IAM) policies that will be used in a DevOps CI/CD pipeline for deployment to an Oracle Container Engine for Kubernetes (OKE) environment. Which OCI IAM policy can be used?
Options
Discussion
Option A fits with what the official docs recommend for DevOps CI/CD setups on OCI. Regular groups are preferred for project admin roles managing devops-family resources, not dynamic groups. Saw similar structure on recent Oracle practice tests. Pretty sure it's A, but open if anyone's seen newer guidance.
A
Its A here. For a DevOps project admin (a user not an automation), you need a regular group managing devops-family. Dynamic groups like in B are for automated resources, not people. Anyone disagree?
B . If the deployment pipeline is fully automated and running as a resource rather than a user, I'd expect a dynamic group (so B) to be common in practice. A lot of folks miss that when pipelines trigger OKE actions, dynamic-group policies are used for permissions. Maybe I'm off if the intent is for actual users, but I don't see why B can't fit here. Open to feedback if I'm missing a subtlety.
Yeah, I'd pick A too. Using a regular group for the deployment pipeline lines up with OCI docs for managing devops-family resources. Dynamic groups are more for automation with compute or functions, not admins. Open to counterpoints if I missed some recent change.
Call it it's A for this, fits what a project admin would use in real-world OCI setups.
Its A, had something like this in a mock recently and A matched the scenario exactly.
Yeah, A looks right here since IAM groups are for real users like project admins, not dynamic groups which are more for automation or OCI resources. The scenario mentions a project admin, so it fits better than B. If the pipeline itself was automated, then it'd be different. Anyone see it another way?
A here. Since the question refers to a DevOps project administrator, that's typically a user assigned to a regular group, not dynamic. Dynamic groups like B are for automations/instances. Pretty sure A is it, but jump in if you see it differently.
I don't think it's B. A is correct since the scenario says "project administrator" and refers to a group, not a dynamic group. Trap here is mixing up dynamic groups (for automated resources) with regular groups for human admins.
Be respectful. No spam.