[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-08 UTC。"],[],[],null,["# Detect suboptimal configurations\n\nThere are suboptimal configurations that are valid and allowed, but are not\ncost-effective and do not follow best practices.\n\nSome common examples of suboptimal configurations are as follows:\n\n- Single-zone deployments\n- Single VPN tunnel without redundancy\n- Single third-party VM as routing or NAT endpoint in the path\n- Load balancer with a single backend\n- External IP address is reserved but not allocated to a resource\n- IP address utilization of a subnet is high (this can prevent automatically creating VMs or upgrading GKE clusters)\n\n### Scenario: High IP address utilization of a subnet\n\nIn this example, an insight from the IP utilization insights category of\n*[high IP address utilization of a subnet](/network-intelligence-center/docs/network-analyzer/insights/vpc-network/ip-utilization#ip-allocation-ratio-high)*\ntype is generated.\n\nThe insight details page shows that the primary range of the subnet has an IP\nallocation value of 100%, which is higher than the threshold value of 75%. This\npage also provides a list of resources that are allocated IP addresses from this\nsubnet. For example:\n\n- 1 forwarding rule\n- 2 reserved static internal IP addresses\n- 1 instance"]]
