The correct options are Static code analysis and Dynamic code analysis.

Static code analysis examines source code or compiled binaries without executing the program to identify coding errors, insecure constructs and patterns that lead to vulnerabilities. It is commonly performed by linters and SAST tools during development and in continuous integration to catch issues early.

Dynamic code analysis evaluates the application while it is running to find flaws that only appear at runtime such as input validation failures, memory issues and configuration problems. DAST tools and runtime instrumentation are used during testing and staging to observe actual behavior under real execution conditions.

Dependency vulnerability scanning focuses on identifying known vulnerabilities in third party libraries and packages rather than analyzing the application code itself. This approach is important for supply chain security and is usually referred to as software composition analysis.

Peer walkthrough review is a manual code review practice where developers inspect each other's code and discuss design and defects. It is a valuable quality activity but it is not one of the automated static or dynamic analysis techniques that the question targets.

Full AWS Practitioner Certification Question