Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Local activity trails are not consolidated into the audit security boundary. The stated evidence instead indicates: Local Config assessments exist but no aggregation exposes cross-account status.

Public ACM-issued certificates were wrongly assumed to provide a corporate private CA chain. The stated evidence instead indicates: Local Config assessments exist but no aggregation exposes cross-account status.

All accounts share one indiscriminate service-control policy despite different risk profiles. The stated evidence instead indicates: Local Config assessments exist but no aggregation exposes cross-account status.

RI purchases are evaluated only in the purchasing account without considering shared billing treatment. The stated evidence instead indicates: On-demand usage was left wholly uncommitted despite predictable baseline compute consumption.

The team relies exclusively on retrospective end-of-month billing statements. The stated evidence instead indicates: On-demand usage was left wholly uncommitted despite predictable baseline compute consumption.

Individual accounts use drifting custom schedules that do not match central backup policy. The stated evidence instead indicates: On-demand usage was left wholly uncommitted despite predictable baseline compute consumption.

Eligible file changes are transferred and verified by a scheduled DataSync task. However, this does not establish the required outcome: new capability traffic can be rolled back while untouched monolith endpoints remain functional.

An end-to-end test request shows linked spans and reveals downstream latency without leaking credentials. However, this does not establish the required outcome: new capability traffic can be rolled back while untouched monolith endpoints remain functional.

A forced downstream failure follows tested compensation logic without duplicating completed orders. However, this does not establish the required outcome: new capability traffic can be rolled back while untouched monolith endpoints remain functional.

This action targets a different technical need: A monolithic Windows process has been decomposed into HTTP services that can run in managed containers without operating its own servers. It does not replace either required solution in A or B. Fargate can run supported ECS container tasks without customer-managed worker hosts; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A business database needs a low-downtime migration from on-premises PostgreSQL to Amazon RDS PostgreSQL. It does not replace either required solution in A or B. AWS DMS can move data using full load and ongoing CDC for supported sources; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A corporation has hundreds of interdependent on-premises services and cannot establish which databases must move together. It does not replace either required solution in A or B. Dependency mapping reduces migration risk by revealing the actual application interaction graph; verify the two stated requirements independently rather than accepting an unrelated change.

Traffic was switched to the container environment before dependent services and probes were verified. The stated evidence instead indicates: A direct S3 SDK rewrite was imposed on workloads that cannot change their file interface.

A non-Kubernetes orchestrator was chosen despite strict Kubernetes extension compatibility requirements. The stated evidence instead indicates: A direct S3 SDK rewrite was imposed on workloads that cannot change their file interface.

Developers assume SQS has identical JMS or broker feature semantics to the source stack. The stated evidence instead indicates: A direct S3 SDK rewrite was imposed on workloads that cannot change their file interface.

The workload uses only on-demand capacity despite safe restart or checkpoint semantics. The stated evidence instead indicates: The CDN forwards every request to origin due to ineffective cache keys or caching headers.

Every static asset fetch goes to a distant origin instead of the edge cache. The stated evidence instead indicates: The CDN forwards every request to origin due to ineffective cache keys or caching headers.

S3 calls egress through NAT because no supported endpoint route was configured. The stated evidence instead indicates: The CDN forwards every request to origin due to ineffective cache keys or caching headers.

This action targets a different technical need: Network administrators must manage a shared subnet centrally while application accounts place their own resources in it. It does not replace either required solution in A or B. VPC sharing separates network ownership from application resource ownership; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A vendor assumes a role into an AWS account and must be restricted to one project's S3 prefix for that session only. It does not replace either required solution in A or B. Session policies intersect with role permissions and can reduce privileges for one temporary session; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Variable monthly expenses must trigger alerts for unusual spending spikes without predefined per-service thresholds. It does not replace either required solution in A or B. Cost Anomaly Detection learns spending patterns and flags unusual expenditures; verify the two stated requirements independently rather than accepting an unrelated change.

Local identity permissions were incorrectly treated as overriding organizational guardrails. The stated evidence instead indicates: The inspection design allows forward and return packets to use different stateful inspection appliances.

A single Direct Connect circuit creates a site-to-cloud connectivity single point of failure. The stated evidence instead indicates: The inspection design allows forward and return packets to use different stateful inspection appliances.

There is no independently functioning VPN path when private connectivity goes down. The stated evidence instead indicates: The inspection design allows forward and return packets to use different stateful inspection appliances.

An all-at-once replacement has unacceptable outage and rollback risk. The specific problem here is that tight synchronous coupling propagates a noncritical downstream failure to the primary transaction.

Dedicated EC2 servers remain the scaling bottleneck for stateless containerized workloads. The specific problem here is that tight synchronous coupling propagates a noncritical downstream failure to the primary transaction.

Local instance disks are wrongly used as a shared durable POSIX file system. The specific problem here is that tight synchronous coupling propagates a noncritical downstream failure to the primary transaction.

A standard read replica is assumed to be a synchronous multi-Region failover mechanism without promotion. The stated evidence instead indicates: No event archive exists to replay notifications that failed during downstream processing.

Every reporting query was sent to the cluster writer endpoint despite available readers. The stated evidence instead indicates: No event archive exists to replay notifications that failed during downstream processing.

Repeated retries of one failed message prevent useful error isolation and redrive workflow. The stated evidence instead indicates: No event archive exists to replay notifications that failed during downstream processing.

WAF rules are deployed without visibility into which requests they affect. The stated evidence instead indicates: Shared costs are assigned by arbitrary percentage without service consumption evidence.

Instances remain oversized based only on purchase history rather than performance evidence. The stated evidence instead indicates: Shared costs are assigned by arbitrary percentage without service consumption evidence.

Teams purchase more RIs independently without measuring existing shared coverage. The stated evidence instead indicates: Shared costs are assigned by arbitrary percentage without service consumption evidence.