Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Eligible file changes are transferred and verified by a scheduled DataSync task. However, this does not establish the required outcome: partners connect over SFTP and transferred objects appear in assigned bucket prefixes.

Replicated servers boot in AWS test VPCs with verified application functionality before cutover. However, this does not establish the required outcome: partners connect over SFTP and transferred objects appear in assigned bucket prefixes.

Vendor-certified testing proves that the appliance runs on the selected target or requires retain/replace decision. However, this does not establish the required outcome: partners connect over SFTP and transferred objects appear in assigned bucket prefixes.

This action targets a different technical need: Attackers continuously probe application URLs and security needs request-level evidence for rule tuning. It does not replace either required solution in A or B. WAF logs provide request and rule evaluation evidence for security tuning; 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: An SNS topic invokes an asynchronous HTTP subscriber with intermittent failures and business needs controlled redelivery. It does not replace either required solution in A or B. SNS subscriber reliability relies on delivery retries and appropriately configured dead-letter destinations; verify the two stated requirements independently rather than accepting an unrelated change.

Console edits accumulate because no one compares deployed state with infrastructure definitions. The specific problem here is that administrators run sensitive maintenance scripts with no enforced approval or trail.

Engineers measure host utilization but not the outcomes experienced by users. The specific problem here is that administrators run sensitive maintenance scripts with no enforced approval or trail.

WAF rules are deployed without visibility into which requests they affect. The specific problem here is that administrators run sensitive maintenance scripts with no enforced approval or trail.

Fixed hot storage is retained for every object because teams cannot forecast access patterns. The stated evidence instead indicates: Unbounded request bursts overload backends because no gateway rate protection is configured.

No event archive exists to replay notifications that failed during downstream processing. The stated evidence instead indicates: Unbounded request bursts overload backends because no gateway rate protection is configured.

Imperative glue retries all upstream steps and creates duplicate side effects. The stated evidence instead indicates: Unbounded request bursts overload backends because no gateway rate protection is configured.

This action targets a different technical need: A Windows estate contains expensive licensed products whose licensing rights differ between shared tenancy and dedicated hosts. It does not replace either required solution in A or B. License entitlements must be assessed before migration architecture and instance selection; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: Branch offices retain file shares locally but need backup and tiered cloud-backed storage without replacing every client. It does not replace either required solution in A or B. Storage Gateway helps bridge supported on-premises storage protocols to AWS-backed storage; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A company must perform recurring secure file synchronization from on-premises NAS into Amazon S3 with minimal custom scripting. It does not replace either required solution in A or B. AWS DataSync automates supported file and object movement with verification features; verify the two stated requirements independently rather than accepting an unrelated change.

A static password in deployment parameters cannot be centrally rotated safely. The specific problem here is that raw CloudTrail logs were collected but no managed threat-detection findings were enabled.

IAM principal permission was mistaken for sufficient access despite a restrictive KMS key policy. The specific problem here is that raw CloudTrail logs were collected but no managed threat-detection findings were enabled.

Storage capacity was fixed without safe growth management under variable data requirements. The specific problem here is that raw CloudTrail logs were collected but no managed threat-detection findings were enabled.

Employees sign in using enterprise identities and receive only the mapped roles in assigned accounts. However, this does not establish the required outcome: every enrolled account produces expected trail events in the security account and workloads cannot delete retained logs.

The consumer role reads approved encrypted objects but cannot decrypt other protected datasets. However, this does not establish the required outcome: every enrolled account produces expected trail events in the security account and workloads cannot delete retained logs.

Eligible compute charges reflect the planned commitment discount and remaining coverage is visible. However, this does not establish the required outcome: every enrolled account produces expected trail events in the security account and workloads cannot delete retained logs.

The inspection design allows forward and return packets to use different stateful inspection appliances. The stated evidence instead indicates: The backup Region exists but DNS routing never changes after primary endpoint failure.

Only source-region S3 versioning is enabled, but no replication rule or role exists. The stated evidence instead indicates: The backup Region exists but DNS routing never changes after primary endpoint failure.

No archive or retention mechanism was configured before the subscriber outage. The stated evidence instead indicates: The backup Region exists but DNS routing never changes after primary endpoint failure.

All accounts share one indiscriminate service-control policy despite different risk profiles. The stated evidence instead indicates: Each application team is provisioning its own disconnected backbone gateway.

Each business unit manually maintains duplicative IAM users in workload accounts. The stated evidence instead indicates: Each application team is provisioning its own disconnected backbone gateway.

Teams have only aggregate bills and cannot locate the source of inefficient storage usage. The stated evidence instead indicates: Each application team is provisioning its own disconnected backbone gateway.

Every component must be rebuilt from scratch after failure, despite a tighter RTO. The stated evidence instead indicates: Records use ordinary simple routing without failover health awareness.

A single active Region was incorrectly advertised as having near-zero recovery time. The stated evidence instead indicates: Records use ordinary simple routing without failover health awareness.

The disaster-recovery Region has no local image copy and the deployment assumes remote registry availability. The stated evidence instead indicates: Records use ordinary simple routing without failover health awareness.

This action targets a different technical need: A department must be notified promptly when monthly spending exceeds its threshold. It does not replace either required solution in A or B. AWS Budgets supports spend targets and notifications on actual or forecasted cost; verify the two stated requirements independently rather than accepting an unrelated change.

This action targets a different technical need: A company uses Direct Connect for normal hybrid traffic but needs encrypted emergency connectivity if carrier circuits fail. It does not replace either required solution in A or B. A tested secondary encrypted tunnel path can carry critical traffic while primary private connectivity is unavailable; 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.