Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Static security policy documents are not technically enforced against resource drift. The specific problem here is that console edits accumulate because no one compares deployed state with infrastructure definitions.

Uncorrelated logs hide where the end-to-end latency accumulates. The specific problem here is that console edits accumulate because no one compares deployed state with infrastructure definitions.

Service-specific Health notifications are not routed into incident processes. The specific problem here is that console edits accumulate because no one compares deployed state with infrastructure definitions.

Replica lag and promotion tests meet defined RPO and RTO targets during planned and simulated events. However, this does not establish the required outcome: a drilled failover boots recoverable instances and meets tested recovery objectives and dependency order.

Backups remain recoverable from the dedicated account even when the application account is disabled. However, this does not establish the required outcome: a drilled failover boots recoverable instances and meets tested recovery objectives and dependency order.

Events from a test member account reach the central incident workflow and unauthorized senders are rejected. However, this does not establish the required outcome: a drilled failover boots recoverable instances and meets tested recovery objectives and dependency order.

Developers assume SQS has identical JMS or broker feature semantics to the source stack. The specific problem here is that a direct S3 SDK rewrite was imposed on workloads that cannot change their file interface.

One-time offline export cannot satisfy the narrow write-freeze window. The specific problem here is that a direct S3 SDK rewrite was imposed on workloads that cannot change their file interface.

Local instance disks are wrongly used as a shared durable POSIX file system. The specific problem here is that a direct S3 SDK rewrite was imposed on workloads that cannot change their file interface.

CloudFront caching addresses repeat web requests and origin transfer, not a governed S3 archive lifecycle or a monitored weighted Lambda release. It provides neither requirement A nor requirement B.

A cross-Region RDS read replica concerns asynchronous database replication and disaster recovery; it neither establishes the dataset storage-class transition nor sends a measured percentage of Lambda traffic to a new published version.

EC2 Spot addresses cost reduction for interruption-tolerant compute jobs. These workstreams require archived-object retention and Lambda deployment routing, not batch compute capacity procurement; Spot does not implement either control.

Migration estimates are based solely on outdated procurement records rather than measured workload behavior. The stated evidence instead indicates: A simple online copy was selected without calculating network capacity and transfer duration.

Database engine migration was assumed to be a simple homogeneous replication job. The stated evidence instead indicates: A simple online copy was selected without calculating network capacity and transfer duration.

All analytics jobs depend on a single custom ETL server and its directly attached storage. The stated evidence instead indicates: A simple online copy was selected without calculating network capacity and transfer duration.

Console-created infrastructure diverged from versioned architecture definitions. The stated evidence instead indicates: A successful compilation is treated as proof that the release is safe and functional.

The function's unqualified ARN always invokes latest code for all users, bypassing version routing. The stated evidence instead indicates: A successful compilation is treated as proof that the release is safe and functional.

Objects remain indefinitely in higher-cost storage despite a proven low-access retention pattern. The stated evidence instead indicates: A successful compilation is treated as proof that the release is safe and functional.

Resource-based trust was not evaluated beyond local IAM identity permission reports. The stated evidence instead indicates: Teams confuse key material rotation with replacing the KMS key ID and losing access to old data.

Role policies retain privileges indefinitely without evidence about actual service usage. The stated evidence instead indicates: Teams confuse key material rotation with replacing the KMS key ID and losing access to old data.

Only instance host metrics exist and individual container bottlenecks cannot be isolated. The stated evidence instead indicates: Teams confuse key material rotation with replacing the KMS key ID and losing access to old data.

Management-account-only operations were mistaken for necessary daily centralized security administration. The stated evidence instead indicates: The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission.

Individual Security Hub instances were not centrally delegated or aggregated. The stated evidence instead indicates: The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission.

Resource policies were never checked for access beyond the organization's trust boundary. The stated evidence instead indicates: The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission.

Previous-month charges were presented as accurate forecasts for an expanded future footprint. The stated evidence instead indicates: Summary monthly bills lack the resource-level usage detail needed for chargeback.

A single-Region DynamoDB table cannot accept the required local writes after that Region fails. The stated evidence instead indicates: Summary monthly bills lack the resource-level usage detail needed for chargeback.

The team relies exclusively on retrospective end-of-month billing statements. The stated evidence instead indicates: Summary monthly bills lack the resource-level usage detail needed for chargeback.

This action targets a different technical need: The security team manages GuardDuty separately in 50 accounts and misses newly created member accounts. It does not replace either required solution in A or B. Central GuardDuty administration supports ongoing multi-account detection enrollment; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A multi-AZ production stack has never been tested with a failed Availability Zone during working hours. It does not replace either required solution in A or B. Fault injection validates real system behavior within approved experiment boundaries; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A database team purchased oversized io2 EBS performance when measured throughput is far below its actual needs. It does not replace either required solution in A or B. EBS volume-class selection should follow measured IO and durability requirements; verify the two stated requirements independently rather than accepting an unrelated change.

Complex heterogeneous schema conversion was selected unnecessarily for a same-engine migration. The specific problem here is that the migration plan assumes a new AWS Snowball Edge device can still be ordered even though new-customer ordering is unavailable.

All assets are scheduled for direct rehost even when some are obsolete or unsuitable. The specific problem here is that the migration plan assumes a new AWS Snowball Edge device can still be ordered even though new-customer ordering is unavailable.

Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover. The specific problem here is that the migration plan assumes a new AWS Snowball Edge device can still be ordered even though new-customer ordering is unavailable.