Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

This action targets a different technical need: A corporate SOC needs one prioritized security findings view across enabled security services and Regions. It does not replace either required solution in A or B. Security Hub consolidates security posture and findings from participating services; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Production maintenance requires an explicit approval and tracked change record before automation updates EC2 systems. It does not replace either required solution in A or B. Controlled automation separates approval from execution and preserves traceability; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Finance collects optimizer suggestions from Compute Optimizer, Trusted Advisor and cost dashboards but counts the same recommendation more than once. It does not replace either required solution in A or B. Consolidated savings recommendations should not be summed blindly across sources; verify the two stated requirements independently rather than accepting an unrelated change.

Database engine migration was assumed to be a simple homogeneous replication job. The stated evidence instead indicates: Homegrown scripts do not handle incremental transfer, scheduling and verification consistently.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The stated evidence instead indicates: Homegrown scripts do not handle incremental transfer, scheduling and verification consistently.

One-time offline export cannot satisfy the narrow write-freeze window. The stated evidence instead indicates: Homegrown scripts do not handle incremental transfer, scheduling and verification consistently.

One overbroad bucket-level policy grants both teams access to all data. The stated evidence instead indicates: Unsupported drivers or unsuitable instance networking features cap throughput.

Cluster compute totals are misleading because the needed task resources are not schedulable. The stated evidence instead indicates: Unsupported drivers or unsuitable instance networking features cap throughput.

Only instance host metrics exist and individual container bottlenecks cannot be isolated. The stated evidence instead indicates: Unsupported drivers or unsuitable instance networking features cap throughput.

Individual account stacks were created manually and drift from the approved baseline. The specific problem here is that in-place overwriting of every production instance removed the healthy comparison environment.

Records use ordinary simple routing without failover health awareness. The specific problem here is that in-place overwriting of every production instance removed the healthy comparison environment.

The function's unqualified ARN always invokes latest code for all users, bypassing version routing. The specific problem here is that in-place overwriting of every production instance removed the healthy comparison environment.

Static IAM user access keys were embedded in the external CI configuration. The stated evidence instead indicates: IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

Unbounded request bursts overload backends because no gateway rate protection is configured. The stated evidence instead indicates: IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

Traffic bypasses inspection endpoints, so rules exist but are never reached. The stated evidence instead indicates: IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy.

The application is exposed to one database host or zonal compute failure. The stated evidence instead indicates: Kubernetes deployment treats process startup as adequate evidence of request readiness.

Threat detection remains inconsistently deployed across member accounts and Regions. The stated evidence instead indicates: Kubernetes deployment treats process startup as adequate evidence of request readiness.

Standard short-lived backups cannot recover the exact chosen accidental-update point. The stated evidence instead indicates: Kubernetes deployment treats process startup as adequate evidence of request readiness.

This action targets a different technical need: Critical backups must be scheduled consistently across many application accounts and retained by policy. It does not replace either required solution in A or B. Organization backup policies support common baseline definitions but still require functioning target configuration; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An organization needs central inspection of east-west traffic from multiple spoke VPCs without asymmetric return flows. It does not replace either required solution in A or B. Stateful network inspection requires symmetric paths through the selected inspection appliance; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Operations needs one centralized queue of cost optimization recommendations from multiple AWS services. It does not replace either required solution in A or B. Cost Optimization Hub consolidates and de-duplicates supported AWS cost recommendations; verify the two stated requirements independently rather than accepting an unrelated change.

An overly broad assumed-role session is not constrained to the vendor's assigned resources. The stated evidence instead indicates: New accounts are assembled by ad hoc scripts with inconsistent security baselines.

Local activity trails are not consolidated into the audit security boundary. The stated evidence instead indicates: New accounts are assembled by ad hoc scripts with inconsistent security baselines.

Local Config assessments exist but no aggregation exposes cross-account status. The stated evidence instead indicates: New accounts are assembled by ad hoc scripts with inconsistent security baselines.

An all-at-once replacement has unacceptable outage and rollback risk. The stated evidence instead indicates: Repeated uncached database work dominates response latency and compute expense.

All analytics jobs depend on a single custom ETL server and its directly attached storage. The stated evidence instead indicates: Repeated uncached database work dominates response latency and compute expense.

Separate component logs cannot be correlated to customer transactions. The stated evidence instead indicates: Repeated uncached database work dominates response latency and compute expense.

IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy. The stated evidence instead indicates: A static password in deployment parameters cannot be centrally rotated safely.

Raw CloudTrail logs were collected but no managed threat-detection findings were enabled. The stated evidence instead indicates: A static password in deployment parameters cannot be centrally rotated safely.

Instance capacity is pinned to one zone with no automated target recovery. The stated evidence instead indicates: A static password in deployment parameters cannot be centrally rotated safely.

This action targets a different technical need: A platform team requires Kubernetes APIs, admission policies and custom controllers while moving a container platform to AWS. It does not replace either required solution in A or B. EKS provides a managed Kubernetes control plane for teams using Kubernetes-native tooling; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A SQL Server estate must migrate to Amazon Aurora PostgreSQL despite vendor-specific T-SQL constructs. It does not replace either required solution in A or B. Heterogeneous database migrations require explicit schema and application compatibility work; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An ecommerce backend repeatedly recomputes expensive reads for product listings that change infrequently. It does not replace either required solution in A or B. Correct cache placement and invalidation reduce repeated work without violating freshness needs; verify the two stated requirements independently rather than accepting an unrelated change.