Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Mainframe batch and transaction semantics were treated as if they were ordinary Linux workloads. The stated evidence instead indicates: Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover.

Migration tasks are tracked in separate team documents with no common portfolio state. The stated evidence instead indicates: Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover.

Traffic was switched to the container environment before dependent services and probes were verified. The stated evidence instead indicates: Manual one-time disk copying cannot keep hundreds of moving workloads synchronized until cutover.

This action targets a different technical need: An EC2 fleet has low utilization and a migration team wants instance-family replacement recommendations backed by memory metrics. It does not replace either required solution in A or B. Compute Optimizer estimates rightsizing opportunities subject to compatibility and workload validation; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An EC2 application needs sustained random IOPS independent of EBS volume storage-size growth. It does not replace either required solution in A or B. gp3 separates baseline volume storage size from configurable IOPS and throughput within limits; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A DynamoDB application requires recovery from accidental writes to an earlier point within a month. It does not replace either required solution in A or B. DynamoDB PITR restores to a selected point within its available recovery window; 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 specific problem here is that individual IAM users were being created per account instead of using centralized workforce federation.

The remote principal has S3 object access but lacks required key-policy and IAM decrypt permission. The specific problem here is that individual IAM users were being created per account instead of using centralized workforce federation.

New accounts are assembled by ad hoc scripts with inconsistent security baselines. The specific problem here is that individual IAM users were being created per account instead of using centralized workforce federation.

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: A distributed transaction takes too long but the application log contains no per-hop timing breakdown. It does not replace either required solution in A or B. Distributed tracing provides span-level request-path visibility across instrumented services; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: An EC2 application needs sustained random IOPS independent of EBS volume storage-size growth. It does not replace either required solution in A or B. gp3 separates baseline volume storage size from configurable IOPS and throughput within limits; verify the two stated requirements independently rather than accepting an unrelated change.

A conversion report identifies unsupported objects and a pilot executes critical queries correctly. However, this does not establish the required outcome: services scale independently and teams do not manage EC2 container worker hosts.

Independently scaled workers can access the same files over supported NFS semantics. However, this does not establish the required outcome: services scale independently and teams do not manage EC2 container worker hosts.

Existing clients publish and consume messages with acceptable protocol compatibility after controlled cutover. However, this does not establish the required outcome: services scale independently and teams do not manage EC2 container worker hosts.

Release decisions reference tracked error rate and latency burn rather than raw instance uptime alone. However, this does not establish the required outcome: simulated or published applicable Health events reach the responsible operations group before planned impact.

A retry resumes the failed state without independently rerunning successful steps and errors are visible in execution history. However, this does not establish the required outcome: simulated or published applicable Health events reach the responsible operations group before planned impact.

Discount usage improves with fewer unused reservation hours and measured baseline cost changes. However, this does not establish the required outcome: simulated or published applicable Health events reach the responsible operations group before planned impact.

This action targets a different technical need: Legal and nonproduction workloads require different organizational guardrails but must share central billing. It does not replace either required solution in A or B. Organizational units help assign governance boundaries to related member accounts; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Hundreds of virtual machines require orchestrated recovery into AWS after a primary on-premises site failure. It does not replace either required solution in A or B. AWS Elastic Disaster Recovery supports block-level replication and automated recovery launches; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Compliance requires protected organization-wide API activity logs to flow into a centralized security account with controlled deletion. It does not replace either required solution in A or B. AWS Organizations trails centralize multi-account CloudTrail logging when storage access is secured; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A personal-health-record system has strict regional data residency and encryption obligations before any cloud transfer. It does not replace either required solution in A or B. Regulatory and data-classification constraints affect target location and migration scope; verify the two stated requirements independently rather than accepting an unrelated change.

An offline snapshot without ongoing change capture is not the low-downtime PostgreSQL-to-RDS migration specified. Use a supported full-load plus CDC migration task, monitor replication lag and perform controlled cutover validation.

Full-load plus CDC can reduce migration downtime, but cutting over with outstanding changes and no consistency verification jeopardizes committed transactions. A monitored replication task, lag threshold and controlled tested cutover are needed.

The workload uses only on-demand capacity despite safe restart or checkpoint semantics. The stated evidence instead indicates: Fixed hot storage is retained for every object because teams cannot forecast access patterns.

Stable compute baseline is paid at on-demand rates without analyzed commitments. The stated evidence instead indicates: Fixed hot storage is retained for every object because teams cannot forecast access patterns.

Stream shard limits or skewed partition keys cannot handle incoming record throughput. The stated evidence instead indicates: Fixed hot storage is retained for every object because teams cannot forecast access patterns.

Storage capacity was fixed without safe growth management under variable data requirements. The stated evidence instead indicates: Traffic bypasses inspection endpoints, so rules exist but are never reached.

Raw CloudTrail logs were collected but no managed threat-detection findings were enabled. The stated evidence instead indicates: Traffic bypasses inspection endpoints, so rules exist but are never reached.

A public bucket policy exposes origin objects outside the intended CloudFront access path. The stated evidence instead indicates: Traffic bypasses inspection endpoints, so rules exist but are never reached.

Backup-only DR cannot restart the platform quickly enough for the required minutes-long RTO. The stated evidence instead indicates: The destination bucket is present but replication cannot use the destination KMS key.

All containers share a single placement failure domain and cannot be rescheduled in time. The stated evidence instead indicates: The destination bucket is present but replication cannot use the destination KMS key.

Traffic bypasses inspection endpoints, so rules exist but are never reached. The stated evidence instead indicates: The destination bucket is present but replication cannot use the destination KMS key.