Question 680
At Global pharmacy vendor, the Google Cloud design for private AI endpoint access is affected because public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts. A review found that network scan finds broad ingress on a model-serving load balancer. The proposed response must account for the requirement that only corporate approved callers may submit sensitive requests. Which controlled implementation should be used to preserve operational continuity during the change?
Explanation
Correct Answer
Migrate known clients to private endpoints and remove public traffic routes is a controlled means to introduce the approved architecture while meeting the requirement that only corporate approved callers may submit sensitive requests. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
The alternative “Use private model-serving access and workload-bound IAM with constrained ingress” describes the chosen design, but not how it is introduced safely. In the reported observation, network scan finds broad ingress on a model-serving load balancer. The option “Migrate known clients to private endpoints and remove public traffic routes” instead addresses the requested controlled implementation.
Obscurity is not an endpoint authorization control. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that only corporate approved callers may submit sensitive requests.
The alternative “Monitor ingress drift and attempted model endpoint abuse” addresses later monitoring rather than the actual controlled deployment. In the reported observation, network scan finds broad ingress on a model-serving load balancer. The option “Migrate known clients to private endpoints and remove public traffic routes” instead addresses the requested controlled implementation.


