Amazon Web Services DOP-C02 Exam With Confidence Using Practice Dumps

 Impact of Removing FullAWSAccess and Adding Policy for EC2 Actions:

The FullAWSAccess policy allows all actions on all resources by default. Removing this policy from the Department OU will limit the permissions that accounts within this OU inherit from the parent OU.

Adding a policy that allows only Amazon EC2 API operations will restrict the permissions to EC2 actions only.

 Permissions of Administrative IAM Roles:

The administrative IAM roles in the Engineering OU have the AdministratorAccess policy attached, which grants full access to all AWS services and resources.

Since SCPs are restrictions that apply at the organizational level, removing FullAWSAccess and replacing it with a policy allowing only EC2 actions means that for all accounts in the Engineering OU:

They will have full access to EC2 actions due to the new SCP.

They will be restricted in other actions that are not covered by the SCP, hence, non-EC2 API actions will be denied.

 Conclusion:

All API actions on EC2 resources will be allowed.

All other API actions will be denied due to the absence of a broader allow policy.

Container restart failures require detailed observability into pod-level, node-level, and container-level metrics and logs. CloudWatch Container Insights is purpose-built for Kubernetes operational diagnostics and provides granular visibility into CPU, memory, network I/O, disk I/O, container restarts, OOM kills, throttling, pod lifecycle issues, and Kubernetes control plane behaviors.

The CloudWatch Observability add-on deploys Fluent Bit and the CloudWatch Agent directly into the EKS cluster as DaemonSets. These components automatically collect:

Container logs

Pod metrics

Node metrics

Cluster events

OOM errors

CrashLoopBackOff restart cycles

Control plane request anomalies

With this data, the DevOps engineer can easily identify misconfigurations, resource bottlenecks, unhealthy nodes, failing containers, or image pull issues.

Option A (dashboards only) lacks per-container diagnostic data.

Option B (CloudTrail) only logs API calls — not useful for restart debugging.

Option C (CloudTrail Insights) only detects anomalous API usage, not container failures.

Therefore, CloudWatch Container Insights is the correct and AWS-recommended solution for diagnosing container restart failures in EKS.

Comprehensive and Detailed Explanation From Exact Extract of DevOps Engineer documents only:

The correct answer is B because AWS Config can continuously evaluate the account-level S3 Block Public Access configuration by using a managed rule. When the configuration becomes noncompliant, AWS Config can trigger automatic remediation through an AWS Systems Manager Automation runbook to restore the required settings.

This solution directly satisfies both requirements:

Detect changes to account-level S3 public access settings.

Automatically revert those changes so that all public access is blocked again.

Why the other options are incorrect:

A. Security Hub is primarily for aggregated security findings and controls visibility. It is not the most direct or standard service for continuous configuration evaluation with automatic remediation of this specific setting.

C. An SCP can restrict permissions, but it does not automatically detect and revert changes to S3 Block Public Access settings.

D. Amazon Macie is for discovering and protecting sensitive data, not for continuously enforcing and remediating S3 Block Public Access account settings.