Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your e-commerce application uses a Memorystore for Redis instance currently configured with DIRECT_PEERING mode. In Cloud Monitoring, you observe that cache hit ratio has dropped from 95% to 58%, memory usage ratio is consistently at 98%, and evicted keys are spiking.
You must resolve this performance degradation while migrating the cache into a Shared VPC architecture with the following requirements:
Which approach should you implement?
Time-to-Live (TTL) defines how long a cached key remains valid before automatic expiration. Private Service Connect (PSC) is a service-centric networking model that surfaces managed or third-party services inside a consumer VPC through a single internal IP forwarding rule (endpoint), avoiding VPC peering.
servicenetworking-googleapis-com connection in the Shared VPC host project./24 or larger for PSA).The workload involved stale, non-hot keys inflating memory usage and the target service was one that natively publishes a Private Service Connect service attachment (such as Cloud SQL with PSC enabled or a third-party SaaS service).
servicenetworking.googleapis.com) in the Shared VPC host project, configure custom route exchange with Cloud Router advertisements, and provision a new higher-capacity Redis instance in PRIVATE_SERVICE_ACCESS mode.Private Services Access is a private networking mechanism that establishes a VPC Network Peering connection between your VPC network and Google's service producer network (servicenetworking.googleapis.com). Combined with provisioning a higher-capacity Memorystore for Redis instance, this approach resolves both the active memory pressure and the architectural networking requirements.
servicenetworking-googleapis-com peering to import and export custom routes (--import-custom-routes and --export-custom-routes) and configuring Cloud Router custom advertised routes for the allocated range allows on-premises clients over Cloud VPN to reach the Redis IP.servicenetworking-googleapis-com peering across services like Cloud SQL and Memorystore, avoiding VPC peering quota exhaustion.usage_ratio, evicted_keys, and cache_hit_ratio.--reserved-ip-range when multiple PSA ranges are allocated.Memorystore for Redis does not allow switching an existing instance from DIRECT_PEERING to PRIVATE_SERVICE_ACCESS in-place. Recreating the instance at a larger tier with PRIVATE_SERVICE_ACCESS simultaneously fixes the cache hit ratio degradation and provides the only supported connectivity model for Shared VPC, Cloud VPN, and centralized IP allocation.
private.googleapis.com, and advertise the private.googleapis.com range over Cloud VPN.Private Google Access (PGA) is a subnet-level feature that allows Compute Engine VMs and GKE nodes without external IP addresses to reach Google's public API endpoints (such as Cloud Storage, BigQuery, and Pub/Sub) over Google's private network using special IP ranges like private.googleapis.com.
private.googleapis.com.servicenetworking-googleapis-com) and PRIVATE_SERVICE_ACCESS mode, you cannot provision a Redis instance in a Shared VPC or route Cloud VPN traffic to its internal IP.private.googleapis.com over Cloud VPN allows on-premises hosts to reach Google APIs privately, but it provides no path to the private subnet where Memorystore for Redis nodes run.Your internal-only GKE nodes and on-premises servers needed private connectivity to public Google Cloud APIs (such as Cloud Storage or BigQuery) rather than a VPC-hosted Memorystore for Redis instance.
connectMode to DIRECT_PEERING with a /29 reserved IP range, and rely on automatic VPC peering for Shared VPC and Cloud VPN access.Direct Peering (DIRECT_PEERING) is a legacy Memorystore for Redis connection mode that automatically creates a dedicated VPC Network Peering connection between a standalone customer VPC and a Google-managed project. In-place scaling increases the memory size of an existing Redis instance without changing its underlying network topology.
DIRECT_PEERING, Memorystore for Redis does not support modifying or migrating an instance's connectMode after creation. Changing networks or connection modes requires recreating the instance.DIRECT_PEERING only supports dedicated, standalone VPC networks and cannot be used to provision or access Redis instances from a Shared VPC service project.DIRECT_PEERING does not support hybrid connectivity from external networks over Cloud VPN or Cloud Interconnect.DIRECT_PEERING is restricted to single-project VPC architectures./29 block is the minimum required only for instances without read replicas; instances with read replicas require at least a /28 block.You only needed to resolve memory pressure by scaling capacity inside a single, standalone VPC network with no Shared VPC, no Cloud VPN access from on-premises systems, and no centralized IP range management across Google Cloud services.
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