Documenting application failure modes and Conducting a peer code walk through are correct because these activities are not typically part of functional testing when the objective is to validate that software behaves according to its specifications and produces expected outputs.

Documenting application failure modes is focused on capturing failure scenarios, root cause analysis and system reliability considerations. This work supports reliability engineering and incident analysis rather than the execution of test cases that verify functional behavior and expected results.

Conducting a peer code walk through is a static review technique that inspects source code and design for defects before or during development. Functional testing is dynamic and requires executing the application with test inputs to confirm that observed outputs match the specified behavior.

Mapping functional requirements to expected behaviors is not correct because it is a core functional testing activity. Testers derive expected results and design test cases from requirements to verify that the software meets its specifications.

Designing test input datasets is not correct because creating input data and scenarios is central to functional testing. Test inputs are used to exercise functionality and validate that the outputs match the expected behaviors.

Full AWS Practitioner Certification Question