"id":"f62dacce-685a-40b7-921d-217699a31f0d","label":null,"text":"Add a new rule above rule 1 to decrypt corp-users traffic.","isCorrect":false},{"id":"aa427a7c-435e-4429-83e8-b62e1804198d","label":null,"text":"Move rule 2 above rule 1.","isCorrect":true},{"id":"cc160ee1-9824-46ee-bb03-56ab5b5316f5","label":null,"text":"Change rule 4 to 'allow' instead of 'block'.","isCorrect":false},{"id":"33a082e6-6519-4518-8465-1a2c36536ed6","label":null,"text":"Change rule 2 to use 'any' for source user.","isCorrect":false}],"domainName":"Decryption and Monitoring","domainSlug":"decryption-monitoring"},{"id":"f33b7c4b-eaf7-4e83-be16-2ce553bdf152","slug":"refer-to-the-exhibit-what-is-the-effect-of-this-configurati-uzw4n","questionText":"Refer to the exhibit. What is the effect of this configuration?","explanation":"The configuration shown is a management profile applied to an interface. The 'ping' service is enabled under the management profile, which allows the firewall to respond to ICMP echo requests (pings) on that specific interface. This does not permit transit ping traffic through the firewall, nor does it enable SSH or allow the firewall to initiate pings. Therefore, option C is correct.","domainId":"731710af-fac7-475e-af04-870ab8bb407c","difficulty":"easy","questionType":"multiple_choice","pbqConfig":null,"exhibitText":"\n PA-220\n none\n 10.0.0.1/24\n allow-ping\n","options":[{"id":"a6c9c465-6f5e-4060-a669-b8802124ac26","label":null,"text":"The firewall allows ping traffic through all interfaces.","isCorrect":false},{"id":"2a83cd3f-6811-4812-bc77-af5c7d6f8253","label":null,"text":"The management profile allows SSH access.","isCorrect":false},{"id":"e4bb8b15-8959-4925-860d-b338dd5ebe94","label":null,"text":"The firewall responds to pings on the management interface.","isCorrect":true},{"id":"32e7c96b-0f61-4385-be01-91bc10075782","label":null,"text":"The firewall cannot ping others.","isCorrect":false}],"domainName":"Device Management and Services","domainSlug":"device-mgmt-services"},{"id":"c36d9be0-5e02-4ae4-b8ce-1824e378fe44","slug":"an-administrator-makes-several-changes-to-the-firewall-confi-q8me7","questionText":"An administrator makes several changes to the firewall configuration and commits. However, after the commit, users report connectivity issues. The administrator wants to revert to the previous configuration quickly without losing the changes that were made earlier in the day but not yet committed. What should the administrator do?","explanation":"The 'commit revert' command in Palo Alto Networks firewalls allows an administrator to revert to the previous committed configuration while preserving any uncommitted changes made after that commit. This is exactly the scenario described: the administrator needs to undo a problematic commit without losing the day's work that has not yet been committed.","domainId":"731710af-fac7-475e-af04-870ab8bb407c","difficulty":"hard","questionType":"multiple_choice","pbqConfig":null,"exhibitText":null,"options":[{"id":"77b8555d-878d-4b07-b1f5-61402506cc0e","label":null,"text":"Issue the 'revert to last known good configuration' command.","isCorrect":false},{"id":"6c11ed55-1e08-4d50-b984-3d4dc4b9e00a","label":null,"text":"Use 'show configuration saved' and copy the previous config.","isCorrect":false},{"id":"5f3aa481-abc5-48cd-9ce7-4bf365a51b77","label":null,"text":"Use the 'commit revert' command to revert to before the problematic commit.","isCorrect":true},{"id":"9fae4a3a-8895-4c1c-9bd3-8d5fd0513f52","label":null,"text":"Reboot the firewall to load the previous running config.","isCorrect":false}],"domainName":"Device Management and Services","domainSlug":"device-mgmt-services"},{"id":"7c06f0e8-3d61-48ad-8edd-d5afca52b17f","slug":"a-network-administrator-is-configuring-a-palo-alto-networks-msl97","questionText":"A network administrator is configuring a Palo Alto Networks firewall in a datacenter. Which TWO traffic types can be inspected by the firewall's Threat Prevention subscriptio