2V0-21.20 · Question #91
An administrator creates a custom ESXi firewall rule using an XML file, however the rules do not appear in the vSphere Web Client. Which action should the administrator take to correct the problem?
The correct answer is B. Load the new rules using esxcli network firewall refresh. Revert the access permissions of the service.xml file to the read-only default by running the # chmod 444 /etc/vmware/firewall/service.xml Refresh the firewall rules for the changes to take effect by running the command: # esxcli network firewall refresh # localcli network…
Question
An administrator creates a custom ESXi firewall rule using an XML file, however the rules do not appear in the vSphere Web Client. Which action should the administrator take to correct the problem?
Options
- ALoad the new rules using esxcli network firewall reload.
- BLoad the new rules using esxcli network firewall refresh.
- CVerify the entries in the XML file and then reboot the ESXi host.
- DRemove the ESXi host from the inventory and add it back.
How the community answered
(27 responses)- A4% (1)
- B81% (22)
- C4% (1)
- D11% (3)
Explanation
Revert the access permissions of the service.xml file to the read-only default by running the # chmod 444 /etc/vmware/firewall/service.xml Refresh the firewall rules for the changes to take effect by running the command: # esxcli network firewall refresh # localcli network firewall refresh
Topics
Community Discussion
No community discussion yet for this question.