t":"Storage vMotion","isCorrect":false},{"id":"6b6076dd-6714-4e38-84e1-4ce03fd23521","label":null,"text":"Export the VM as OVF and import it to the other vCenter","isCorrect":false}],"domainName":"vSphere Architecture, Products and Solutions","domainSlug":"vsphere-architecture"},{"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":"Increasing maxKeepAliveTimeout to a higher value, such as 180, would most likely resolve the issue of HTTP connections timing out frequently. The maxKeepAliveTimeout 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.","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":"03b1b584-aafd-4b91-90f5-340982dee6bb","slug":"what-is-the-maximum-number-of-paths-that-vsphere-supports-fo-c6m1i","questionText":"What is the maximum number of paths that vSphere supports for a single storage device?","explanation":"vSphere supports up to 32 paths per storage device. 4 paths is common for some arrays, 8 is typical but not the maximum, and 256 is too high.","domainId":"39c12252-7629-4712-a6f4-d5cd25547f5f","difficulty":"easy","questionType":"multiple_choice","pbqConfig":null,"exhibitText":null,"options":[{"id":"c51ade6b-8f8b-4690-acb1-80c6e0e2ce30","label":null,"text":"8","isCorrect":false},{"id":"a6eca74d-d06d-4d03-9a5e-724a6975cb6b","label":null,"text":"256","isCorrect":false},{"id":"e70a26b7-cde1-4c58-a9b4-d0c075637138","label":null,"text":"32","isCorrect":true},{"id":"8e27c9c8-f33b-427a-863b-e0758633b8bf","label":null,"text":"4","isCorrect":false}],"domainName":"Configure and Manage vSphere Storage","domainSlug":"vsphere-storage"},{"id":"a52e8ddc-b0f2-4831-9fd0-686261e66db2","slug":"the-administrator-configured-this-lag-on-a-distributed-switc-3yrsg","questionText":"The administrator configured this LAG on a distributed switch and corresponding LACP settings on the physical switch. But the LAG is not coming up. What is a likely issue?","explanation":"When both the vSphere distributed switch LAG and the physical switch are configured in passive mode, LACP negotiation fails because neither side initiates the negotiation. One side must be set to active for LACP to establish. Option A is incorrect because the load balancing policy (e.g., IP hash) is separate from LACP mode; it controls traffic distribution, not LACP negotiation. Option B is incorrect because the LAG name is not used by LACP; LACP uses system identifiers and port keys, so a name mismatch does not prevent the LAG from coming up. Option D is incorrect because active/active mode refers to the uplink teaming policy, not the LACP mode setting.","domainId":"71cfab02-b9f9-4af7