eepAliveTimeout setting controls how long the ESXi host's reverse proxy (rhttpproxy) keeps an HTTP connection open for keep-alive requests. If it is too low, connections may time out prematurely, causing frequent timeouts. Increasing it allows longer-lived connections.","examTrap":"The trap is thinking that restarting the service or disabling keep-alive solves the problem, when the actual fix is to adjust the timeout value. Candidates may also confuse this with proxy settings, which are unrelated to inbound connection timeouts.","examTip":null,"technicalDeepDive":"The rhttpproxy service on ESXi handles HTTP and HTTPS traffic to the host, including the vSphere Client and API. The maxKeepAliveTimeout parameter (configurable via the ESXi host's advanced settings, e.g., using esxcli system settings advanced set -o /UserVars/ESXiRhttpproxyMaxKeepAliveTimeout) defines the maximum time in seconds that a connection can remain idle before being closed. If clients frequently experience timeouts, it may be because the timeout is too short for the network latency or client behavior. Increasing it can help maintain persistent connections. However, setting it too high can consume resources. In real-world scenarios, administrators tune this value based on network conditions and client requirements.","keyConcepts":[],"faqs":[],"eliminationLogic":null,"exhibitText":"Refer to the exhibit.\n\nConfiguration snippet from /etc/vmware/rhttpproxy/config.xml on an ESXi host:\n```\n\n \n false\n \n 0\n \n \n 100\n \n\n```","exhibitUrl":null,"hasExhibit":false,"isExhibitQuestion":false,"questionPairs":null,"hasMatchingPairs":false,"isMatchingQuestion":false,"relatedQuestions":[],"breadcrumbItems":null,"nextQuestionUrl":null,"previousQuestionUrl":null,"domainPracticeUrl":null,"certificationUrl":null,"domainUrl":null,"hasAnswerOptions":true,"updatedAt":"2026-09-20T03:09:32.355+00:00","questionType":"multiple_choice"},{"id":"e6eeb052-816b-496a-94c2-6bd301c5e305","slug":"an-organization-is-using-vsphere-trust-authority-vta-to-se-15oqv","certificationSlug":"vmware-vcp-dcv","examCode":"VCP-DCV","examName":"VMware Certified Professional Data Center Virtualization VCP-DCV","questionText":"An organization is using vSphere Trust Authority (vTA) to secure ESXi hosts. A newly added ESXi host fails to attest with the Trust Authority. The administrator verifies that the host is connected to the vTA cluster and the trust relationship is configured. What is the most likely cause of the attestation failure?","difficulty":"medium","domain":"vSphere Security","domainSlug":"vsphere-security","topic":"","questionNumber":0,"totalQuestions":0,"options":[{"key":"A","isCorrect":false,"text":"The Trust Authority's network is isolated from the ESXi host's management network.","explanation":"vTA requires network connectivity but not necessarily the same network.","masteryContext":""},{"key":"B","isCorrect":false,"text":"The ESXi host is not in the same cluster as the Trust Authority.","explanation":"Attesting hosts are deliberately kept in a separate cluster from the Trust Authority cluster; membership in the same cluster is not required and is in fact discouraged. It is tempting because cluster membership usually governs trust relationships, but vTA works across clusters once the trust and network path are configured.","masteryContext":""},{"key":"C","isCorrect":false,"text":"The ESXi host does not have a virtual Trusted Platform Module (vTPM) attached.","explanation":"vTA attestation validates boot measurements and host identity; a vTPM is not a prerequisite for attesting to the Trust Authority. It is tempting because vTPMs underpin features such as VM encryption and virtual TPM-based attestation in other contexts, but their absence does not cause vTA attestation failure.","masteryContext":""},{"key":"D","isCorrect":true,"text":"The TPM on the ESXi host is disabled or not properly initialized.","exp