The correct answer is Syntax checking, approved API or library usage, and semantic validation of code logic and call structures.

Static code analysis inspects source and build artifacts to perform syntax checking and to enforce patterns for approved API or library usage. It can also apply semantic checks by building control flow and call graphs to find suspicious logic and improper call structures. These techniques work without running the program because they reason about code structure, types, and data flow.

Syntax checks, allowed function calls, and attempting to detect race conditions is incorrect because attempting to detect race conditions reliably requires dynamic information about thread scheduling and runtime behavior. Static tools can flag potential concurrency issues but they cannot definitively detect all race conditions from code alone.

Cloud Trace is incorrect because it is a runtime distributed tracing service and not a category of static code analysis. It collects traces from running services and does not analyze code in a repository.

Syntax validation, permitted libraries, and runtime memory usage profiling is incorrect because runtime memory usage profiling requires executing the program with profilers or instrumentation. Static analysis cannot measure actual memory usage at runtime even though it can flag code patterns that might lead to high memory use.

Full AWS Practitioner Certification Question