The correct answer is To replicate typical user sessions and transactions.

Using a synthetic workload in a security simulation lets testers emulate realistic customer behavior across the retail payments flows. This approach exercises end to end components such as authentication, authorization, clearing and settlement and third party integrations while keeping the inputs controlled and repeatable so that security telemetry and detection rules can be evaluated.

Running To replicate typical user sessions and transactions is particularly valuable for finding business logic flaws, session management issues, and transaction handling gaps that only appear during real world request sequences rather than single isolated checks.

The option To perform cryptographic algorithm verification is incorrect because cryptographic verification requires targeted algorithm tests and validation tools. Those checks are performed at the library or component level and do not depend on emulating user session workflows.

The option To create unpredictable input datasets is incorrect because generating unpredictable or malformed inputs is the domain of fuzzing and random testing. Synthetic workloads are typically controlled and repeatable so that results and alerts can be measured reliably.

The option To stress the infrastructure at peak capacity is incorrect because stress and load testing intentionally push systems to resource limits to measure performance and resilience. Although synthetic workloads can be scaled for load tests their primary use in this context is to mirror normal user transactions for security validation rather than to drive the system to failure.

Full AWS Practitioner Certification Question