QuestionQ66

VerifiedSecuring and governing agentic workflows

You are designing an agentic workflow on Google Cloud for a healthcare enterprise that processes protected health information (PHI) subject to strict HIPAA regulation. Your organization’s security policy prohibits sending PHI over public software-as-a-service (SaaS) internet endpoints and requires full data isolation, customer-managed encryption, and strict data residency. You need to select and deploy language models that support agentic tool calling while meeting these data sovereignty requirements.

What should you do?

Choose two
Explanation

Private Service Connect can route access to Google APIs through a private endpoint, while customer-managed encryption keys provide control over supported encryption-at-rest resources. A self-hosted Gemma deployment on GKE can also support tool calling and keep inference within a controlled environment. (docs.cloud.google.com)

Both approaches require careful configuration of the permitted region and all PHI-bearing resources. For the GKE deployment, CMEK must be configured separately; Private Service Connect alone does not create an air gap or guarantee compliance. (docs.cloud.google.com)

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!