An enterprise is designing a hardened infrastructure baseline on Google Cloud for a self-managed machine learning training pipeline. The training workloads will execute on a Google Kubernetes Engine (GKE) cluster utilizing GPU-accelerated node pools. The organization has mandated the following security requirements: Model weights and sensitive training dataset features must be encrypted in memory during active runtime computation (data-in-use protection). Worker nodes must be protected against boot-level and kernel-level rootkits, enforcing cryptographic verification of the boot chain. Training pods must securely authenticate to Google Cloud APIs (such as Cloud Storage and Artifact Registry) using least-privilege IAM roles without exposing host node VM service account tokens or using legacy metadata concealment. Node instances must have no external IP addresses and must reach Google APIs privately. Which combination of infrastructure and platform security controls fulfills these requirements?

Enable Confidential GKE Nodes for in-use memory encryption, enable Shielded GKE Nodes with Secure Boot and Integrity Monitoring, configure Workload Identity Federation for GKE, and create a private cluster with Private Google Access.: ### What this solution is This architecture combines hardware-level isolation, cryptographically verified boot integrity, secure cloud identity federation, and private networking to establish a zero-trust computing baseline for sensitive artificial intelligence (AI) and machine learning (ML) training workloads on **Google Kubernetes Engine (GKE)**. ### How it meets the requirements - **Protects data in memory (Data-in-Use)**: **Confidential GKE Nodes** leverage hardware-based memory encryption technologies (such as AMD SEV / SEV-SNP) to encrypt data in main memory (RAM) with hardware-managed keys, ensuring that model weights and raw training datasets remain protected from physical memory attacks, hypervisor inspection, and host-level snooping. - **Prevents rootkits and verifies boot integrity**: **Shielded GKE Nodes** provide **Secure Boot**, **Virtual Trusted Platform Module (vTPM)**, and **Integrity Monitoring**. Secure Boot cryptographically inspects and validates bootloaders, kernel modules, and system drivers against authorized signatures to block boot-level or kernel-level rootkits. - **Least-privilege workload authentication**: **Workload Identity Federation for GKE** seamlessly binds Kubernetes Service Accounts (KSAs) to Google Cloud IAM Service Accounts. This eliminates the need to grant broad permissions to node-level service accounts or maintain static keys, completely securing the instance metadata server against pod-level credential extraction and replacing legacy metadata concealment. - **Private networking**: Configuring a **private GKE cluster** with **Private Google Access** ensures worker nodes receive only internal RFC 1918 IP addresses while allowing them to communicate securely and privately with Google APIs (e.g., Cloud Storage and Artifact Registry). ### Key advantages - **Hardware memory isolation**: Secures model intellectual property directly inside CPU/memory architectures. - **Firmware and kernel integrity**: Emits alerts and logs via Cloud Monitoring and Security Command Center if node baseline measurements deviate. - **Fine-grained IAM scoping**: Allows individual training jobs to authenticate to specific Cloud Storage buckets without node-level token sharing. - **Zero external exposure**: Mitigates direct internet-borne attacks by eliminating public IP endpoints on worker nodes. ### Why this is optimal This approach adheres directly to Google Cloud security best practices for AI/ML workloads by combining Confidential Computing with native GKE hardening controls without operational friction or deprecated features.

Gke Confidential Shielded Nodes Ai Training | Professional Cloud Security Engineer

Gke Confidential Shielded Nodes Ai Training

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise is designing a hardened infrastructure baseline on Google Cloud for a self-managed machine learning training pipeline. The training workloads will execute on a Google Kubernetes Engine (GKE) cluster utilizing GPU-accelerated node pools. The organization has mandated the following security requirements:

Model weights and sensitive training dataset features must be encrypted in memory during active runtime computation (data-in-use protection).
Worker nodes must be protected against boot-level and kernel-level rootkits, enforcing cryptographic verification of the boot chain.
Training pods must securely authenticate to Google Cloud APIs (such as Cloud Storage and Artifact Registry) using least-privilege IAM roles without exposing host node VM service account tokens or using legacy metadata concealment.
Node instances must have no external IP addresses and must reach Google APIs privately.

Which combination of infrastructure and platform security controls fulfills these requirements?

Enable Confidential GKE Nodes for in-use memory encryption, enable Shielded GKE Nodes with Secure Boot and Integrity Monitoring, configure Workload Identity Federation for GKE, and create a private cluster with Private Google Access.

Define a VPC Service Controls perimeter encompassing Cloud Storage, disable Secure Boot to ensure third-party driver compatibility, and configure HostNetwork on training pods.

Deploy standard Compute Engine N2 nodes with OS Login enabled, configure client-side encryption (CSE) for GPU VRAM, and enable legacy v0.1 metadata server endpoints.

Configure Customer-Managed Encryption Keys (CMEK) on node persistent disks, enable deprecated metadata concealment (--workload-metadata=SECURE), and use default Compute Engine service accounts with network tags.

Professional Cloud Security Engineer

Gke Confidential Shielded Nodes Ai Training

Related questions