se}],"domainName":"Configure and Manage vSphere Storage","domainSlug":"vsphere-storage"},{"id":"a7da3abf-b4a7-4c81-9f3a-a2b13a205004","slug":"an-administrator-notices-that-http-connections-to-the-esxi-h-hc750","questionText":"An administrator notices that HTTP connections to the ESXi host are timing out frequently. Based on the exhibit, which configuration change would most likely resolve the issue?","explanation":"The maxKeepAliveTimeout default of 100 seconds may be too low for long-lived HTTP connections, causing timeouts. Increasing it to 180 seconds allows the server to keep idle connections open longer, reducing the likelihood of timeouts. Option B is incorrect because restarting the rhttpproxy service does not change the timeout value; it only temporarily resets the service, which would not address the underlying timeout issue. Option C is incorrect because enabling a proxy server is unrelated to HTTP connection timeouts; it would add an intermediary but not resolve the keepalive timeout. Option D is incorrect because setting maxKeepAliveTimeout to 0 disables HTTP keepalive entirely, which would force new connections for every request, likely increasing latency and timeouts rather than resolving them.","domainId":"0c069214-3947-4627-b796-3b475beddccc","difficulty":"medium","questionType":"multiple_choice","pbqConfig":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```","options":[{"id":"c070e665-dba9-4358-8a49-17f04e78bbfd","label":null,"text":"Increase maxKeepAliveTimeout to a higher value, such as 180","isCorrect":true},{"id":"d91b7d74-c4dc-4316-b6e8-2e05c49e1c73","label":null,"text":"Restart the rhttpproxy service","isCorrect":false},{"id":"d426e6d5-4b6c-4ebd-b5f2-74eba3edfb56","label":null,"text":"Set useProxy to true and specify a proxy server","isCorrect":false},{"id":"6481ae32-3cab-4645-b601-291a4e2773b8","label":null,"text":"Set maxKeepAliveTimeout to 0 to disable keepalive","isCorrect":false}],"domainName":"vSphere Security","domainSlug":"vsphere-security"},{"id":"5d596602-6879-4053-bcdf-30de77005951","slug":"an-administrator-is-planning-a-vmotion-migration-and-wants-t-vsn0z","questionText":"An administrator is planning a vMotion migration and wants to minimize the performance impact on the virtual machines during the migration. Which network configuration is recommended?","explanation":"A dedicated VMkernel interface for vMotion isolates migration traffic from other network traffic, reducing contention and ensuring consistent performance. A minimum of 10 GbE is recommended to handle the high throughput demands of vMotion, especially for large VMs. Option B is incorrect because using the default management interface can lead to resource contention and performance degradation. Option C is incorrect because a single 1 GbE interface for both vMotion and management is likely insufficient and causes competition. Option D is incorrect because jumbo frames alone do not address the contention issue; keeping vMotion on the management network still causes competition.","domainId":"65bb5a57-b21c-4b90-83c2-972843a76987","difficulty":"easy","questionType":"multiple_choice","pbqConfig":null,"exhibitText":null,"options":[{"id":"f69739a4-c0db-4b60-9cca-3a5ae4c607c3","label":null,"text":"Create a dedicated VMkernel interface with at least 10 GbE throughput for vMotion.","isCorrect":true},{"id":"dbba82b2-c1a3-4703-a0d9-f1d3b563557d","label":null,"text":"Use the default management VMkernel interface for vMotion traffic.","isCorrect":false},{"id":"dc5963c4-61b3-40c5-88ad-73a51eacb293","label":null,"text":"Configure a single 1 GbE interface for both vMotion and management traffic.","isCorrect":false},{"id":"e064331d-c6d7-424c-95b1-3da2b450d00d","label":null,"text":"Enable jumbo frames on all interfaces, but keep vMotion on the managemen