[[["容易理解","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-04 (世界標準時間)。"],[],[],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"]]
