Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise runs microservices on Google Kubernetes Engine (GKE) and Compute Engine instances. To protect critical assets, the production workloads are enclosed within a VPC Service Controls perimeter. As part of ensuring operational excellence and production reliability, the security team needs to perform automated vulnerability assessments on container images and running workloads without breaking perimeter security or violating the Google Cloud shared responsibility model.
Which configuration should the security team implement?
This approach involves launching high-volume Layer 3 and Layer 4 distributed denial-of-service (DDoS) flood tests aimed directly at the physical network hardware and data center infrastructure managed by Google Cloud.
The goal was to test physical infrastructure resilience in a self-hosted, privately owned on-premises data center where the customer owns all physical network switching hardware.
This option configures the service mesh to bypass sidecar proxies and disable mutual TLS (mTLS) and authorization policies, transmitting internal microservice traffic in plaintext so unauthenticated scanners can inspect packets.
You were intentionally troubleshooting legacy, non-mesh-compatible network protocols within an isolated testing environment that has alternative encryption mechanisms.
This option temporarily disables the VPC Service Controls perimeter and assigns broad, primitive Owner (roles/owner) privileges to external security testers to simplify access during scanning exercises.
roles/securitycenter.adminViewer or roles/securitycenter.findingsViewer) necessary for assessment.You were initializing a completely empty sandbox project for development where no security controls or sensitive production data were present.
Artifact Analysis and Security Command Center (SCC) Vulnerability Assessment provide comprehensive, automated vulnerability scanning for container images and cloud workloads. Under Google Cloud's shared responsibility model, customers are responsible for securing and auditing their application code, container images, and runtime configurations, while Google secures the underlying physical and hypervisor infrastructure.
Cloud Security Command Center Service Agent allows SCC vulnerability scanners to inspect protected resources without dismantling perimeter controls.This approach aligns with Google Cloud security best practices by enabling continuous, deep vulnerability assessment across containerized workloads while respecting perimeter boundaries established by VPC Service Controls.
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