The correct choice is Configure the API cache for full request caching and turn on encryption for data at rest and in transit. This option meets the performance need for low latency on read heavy queries and the compliance need to protect PHI.

Using full request caching stores entire GraphQL responses which increases cache hit rates for repeated queries and lowers response times. Enabling encryption for data at rest and in transit ensures cached data is protected while stored and while transmitted which satisfies HIPAA requirements for PHI.

Enable per-resolver caching and keep the default cache encryption settings is not ideal because per resolver caching only applies to selected resolvers and keeping default encryption can leave cache data unprotected which fails HIPAA.

Leave caching disabled by selecting None and enable encryption for data at rest and in transit secures the data but provides no caching benefits so it does not address the latency goal for read heavy workloads.

Configure the API cache for full request caching and keep the default encryption settings improves read performance but leaving default encryption settings risks unencrypted cached data which does not meet HIPAA requirements.

Full AWS Practitioner Certification Question