Refer to the exhibit. A team created this dedicated AI cluster. However, when they try to create a model deployment, the deployment fails with an error indicating insufficient public IPs. What change to the cluster configuration should they make?
Correct: Enabling public IPs allows nodes to have public endpoints.
Why this answer
The error indicates insufficient public IPs because the cluster's subnet does not have enough available public IP addresses. Setting `assignPublicIp` to `true` in the cluster configuration allows the cluster to automatically allocate public IPs from the subnet's pool, resolving the shortage. This is required for model deployments that need public endpoints.
Exam trap
The trap here is that candidates might think the issue is a subnet IP shortage (Option C) or a scaling problem (Option B), when the real cause is a misconfigured public IP assignment flag that prevents the cluster from using available IPs.
How to eliminate wrong answers
Option B is wrong because increasing the nodeCount to 8 would require even more public IPs, exacerbating the shortage rather than fixing it. Option C is wrong because attaching a different subnet with more public IPs is a workaround, but the root cause is that the cluster is not configured to assign public IPs; changing the subnet does not enable the assignment. Option D is wrong because changing the AI cluster shape to VM.GPU.A10.2 does not affect public IP allocation; it only changes the GPU type and compute capacity.