Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
Your data engineering team needs SSH access to a Compute Engine VM that orchestrates data ingestion pipelines. The VM is located inside a VPC Service Controls perimeter to prevent data exfiltration.
The engineers are working remotely from unmanaged client devices. You need to provide secure SSH access to the VM without exposing it directly to the public internet, while ensuring the access complies with the VPC Service Controls perimeter restrictions.
What should you do?
Device posture evaluation is a context-aware security feature where Access Context Manager analyzes signals from a client device (such as OS version, disk encryption status, or screen lock enforcement) before granting access to resources.
The scenario explicitly states that the engineers are working from unmanaged client devices. Access Context Manager relies on tools like Chrome Enterprise Premium and Endpoint Verification to collect device signals. If a device is unmanaged, these tools are not installed or controlled by the organization, meaning no device posture signals are available to evaluate.
The engineers were using corporate-issued, managed workstations with Endpoint Verification installed, allowing the organization to securely verify the health and configuration of the devices before granting SSH access.
Assigning an external IP address makes a VM directly routable from the public internet. A VPC firewall rule can then be configured to restrict inbound traffic on port 22 (SSH) to a specific list of allowed source IP addresses.
You were operating in a legacy network architecture without Identity-Aware Proxy, and the security policy explicitly mandated perimeter firewall IP allowlisting as the sole method of access control.
Identity-Aware Proxy (IAP) TCP-forwarding acts as an intermediary that allows users to establish secure SSH connections to VM instances without requiring the VM to have a public IP address. VPC Service Controls ingress rules allow explicitly defined external traffic to cross the security perimeter boundary based on context-aware attributes.
This approach leverages Google Cloud's native zero-trust capabilities. It securely bridges the gap between unmanaged external devices and a highly restricted VPC Service Controls perimeter by relying on identity and IP-based context rather than impossible device posture checks.
Cloud VPN establishes a site-to-site IPsec virtual private network connection between an on-premises network and a Google Cloud VPC. OS Login manages SSH access to Compute Engine instances using IAM roles and can enforce 2-step verification.
While OS Login is a best practice for SSH management, configuring a site-to-site Cloud VPN tunnel to individual, unmanaged remote client devices is architecturally incorrect. Cloud VPN is designed to connect entire networks (like a corporate office), not individual remote workers.
The engineers were working from a centralized, trusted corporate office with a dedicated hardware VPN gateway, and you needed to establish a persistent, encrypted site-to-site connection to the VPC.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated