아니요. 구성 분석은 Google Cloud 프로젝트의 리소스 구성을 기반으로 패킷을 추적합니다. 맞춤설정된 이미지를 사용하는 가상 머신(VM) 인스턴스의 경우 연결 테스트가 전달 또는 라우팅 구성에 액세스할 수 없습니다. 그러나 연결 테스트는 예를 들어 Cloud NAT 게이트웨이 VM에 대한 연결 문제를 추적할 수 있으므로 여전히 유용합니다. 이 구성 유형의 예시로는 Cloud NAT 게이트웨이 역할을 하는 VM 또는 Palo Alto Networks VM 시리즈와 같은 타사 방화벽 역할을 하는 VM이 있습니다. 마찬가지로 실시간 데이터 영역 분석도 소스에서 전달 VM까지의 연결 가능성만 테스트합니다.
[[["이해하기 쉬움","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(UTC)"],[],[],null,["# Frequently asked questions\n\nThis document covers commonly asked questions about Connectivity Tests.\n\nDoes Connectivity Tests send a trace packet through my VPC network?\n-------------------------------------------------------------------\n\nYes, it does (for supported configurations). The live data plane analysis\nfeature tests connectivity by sending multiple trace packets from the source\nendpoint to the destination. For details, see the following pages:\n\n- [What is reachability?](/network-intelligence-center/docs/connectivity-tests/concepts/overview#what-is-reachability)\n\n- [How Connectivity Tests works](/network-intelligence-center/docs/connectivity-tests/concepts/overview#how-it-works)\n\n- [Supported configurations (live data plane analysis)](/network-intelligence-center/docs/connectivity-tests/concepts/overview#supported-dynamic-configs)\n\nCan I test a configuration where I enabled the forwarding functions of my VM instance?\n--------------------------------------------------------------------------------------\n\nNo. The configuration analysis traces a packet based on the configuration of\nresources in your Google Cloud projects. For virtual machine (VM) instances\nthat use a customized image, Connectivity Tests doesn't have access to\nthe forwarding or routing configurations. However, Connectivity Tests\nis still helpful in such cases because you can trace connectivity issues to your\nCloud NAT gateway VM, for example. Some examples of this type of configuration\nare a VM acting as a Cloud NAT gateway, or a VM acting as a third-party\nfirewall, such as the Palo Alto Networks VM series. Similarly, live data plane\nanalysis tests reachability only from the source to the forwarding VM.\n\nWhy Connectivity Tests produces multiple traces for a given test?\n-----------------------------------------------------------------\n\nThe Connectivity Tests configuration analysis can show multiple traces\nin the following situations:\n\n- The destination is a load balancer. For more information, see [Number of traces in a test to a load balancer](/network-intelligence-center/docs/connectivity-tests/concepts/test-load-balancers#number-of-traces).\n- ECMP routing is being used. In this case, Connectivity Tests configuration analysis shows a trace for each possible route.\n- The source endpoint has an ambiguous definition. For example, a project can have multiple entities with the same IP address, in different Virtual Private Cloud networks. In this case, Connectivity Tests configuration analysis shows a trace for each source entity.\n\nLive data plane analysis doesn't provide a breakdown into multiple traces.\n\nWhat's next\n-----------\n\n- [Learn about Connectivity Tests](/network-intelligence-center/docs/connectivity-tests/concepts/overview)\n- [Troubleshoot Connectivity Tests](/network-intelligence-center/docs/connectivity-tests/support/troubleshooting)"]]
