Answer-first summary for fast verification
Answer: Explicitly reference the custom mode networks in the Deployment Manager templates.
When converting an auto mode VPC to custom mode, existing subnets remain, but new regions do not auto-create subnets. Deployment Manager templates might fail if they implicitly rely on auto-created subnets or networks. Custom mode VPCs require explicit subnet definitions. Updating the templates to explicitly reference the custom mode networks (e.g., specifying subnets or network paths) ensures resources are provisioned correctly. Options A, B, and C relate to IAM, firewall rules, or Cloud Armor, which are unrelated to Deployment Manager's network references in templates.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
After converting an auto mode VPC network to custom mode, some Cloud Deployment Manager templates have stopped functioning.
How should you resolve this issue?
A
Apply an additional IAM role to the Google API's service account to allow custom mode networks.
B
Update the VPC firewall to allow the Cloud Deployment Manager to access the custom mode networks.
C
Explicitly reference the custom mode networks in the Cloud Armor whitelist.
D
Explicitly reference the custom mode networks in the Deployment Manager templates.
No comments yet.