{"id":21599,"date":"2026-09-25T06:27:22","date_gmt":"2026-09-25T06:27:22","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21599"},"modified":"2026-09-25T06:27:22","modified_gmt":"2026-09-25T06:27:22","slug":"checkpoint-156-536-practice-test-questions-and-exam-dumps-part10-q181-200","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/checkpoint-156-536-practice-test-questions-and-exam-dumps-part10-q181-200\/","title":{"rendered":"Checkpoint 156-536 Practice Test Questions and Exam Dumps Part10 Q181-200"},"content":{"rendered":"

View Full <\/b>Checkpoint 156-536 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/p>\n


\n<\/b>Question 181. What does Endpoint Firewall control?<\/b><\/p>\n

    \n
  1. <\/b> Disk encryption<\/span><\/li>\n
  2. <\/b> Network traffic<\/span><\/li>\n
  3. <\/b> Malware signatures<\/span><\/li>\n
  4. <\/b> Application inventory<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. Network traffic<\/b><\/p>\n

    Explanation:<\/b><\/p>\n

    Harmony Endpoint Firewall controls network traffic entering and leaving managed endpoint computers. Rules can make decisions based on connection details such as IP addresses, ports, protocols, network objects, and services. The firewall policy contains separate inbound and outbound rule bases so administrators can apply different controls to traffic reaching the endpoint and traffic originating from it. This host-based protection remains valuable when endpoints move between corporate and external networks because enforcement occurs directly on the protected device.<\/span><\/p>\n

    Question 182. What does an inbound Firewall rule control?<\/b><\/p>\n

      \n
    1. <\/b> Outgoing web traffic<\/span><\/li>\n
    2. <\/b> Application installation<\/span><\/li>\n
    3. <\/b> Disk access<\/span><\/li>\n
    4. <\/b> Traffic reaching the endpoint<\/span><\/li>\n<\/ol>\n

      Correct Answer: 4. Traffic reaching the endpoint<\/b><\/p>\n

      Explanation:<\/b><\/p>\n

      Inbound Firewall rules determine which network traffic is allowed to reach the endpoint computer. Check Point refers to the endpoint as localhost in this context. Administrators can allow all incoming traffic or restrict incoming connections to trusted zones and required connectivity services, with additional rules added as necessary. Inbound filtering helps prevent unauthorized systems from initiating connections to endpoint devices. Because the destination is always the local endpoint, the classic R81.20 inbound rule base does not require a separate destination column for ordinary rule definition.<\/span><\/p>\n

      Question 183. What does an outbound Firewall rule control?<\/b><\/p>\n

        \n
      1. <\/b> Traffic leaving the endpoint<\/span><\/li>\n
      2. <\/b> Incoming traffic only<\/span><\/li>\n
      3. <\/b> Encryption recovery<\/span><\/li>\n
      4. <\/b> User authentication<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. Traffic leaving the endpoint<\/b><\/p>\n

        Explanation:<\/b><\/p>\n

        Outbound Firewall rules control network connections initiated from the endpoint computer toward other systems or networks. Administrators can allow all outbound traffic or restrict it to trusted zones and common internet protocols, then customize the generated rule base as needed. Because the source of outbound traffic is the endpoint itself, the classic outbound rule base does not require a separate source column. Outbound filtering can reduce the ability of unauthorized applications or malicious processes to communicate externally.<\/span><\/p>\n

        Question 184. In what order are Firewall rules enforced?<\/b><\/p>\n

          \n
        1. <\/b> Bottom to top<\/span><\/li>\n
        2. <\/b> Random order<\/span><\/li>\n
        3. <\/b> Top to bottom<\/span><\/li>\n
        4. <\/b> Alphabetically<\/span><\/li>\n<\/ol>\n

          Correct Answer: 3. Top to bottom<\/b><\/p>\n

          Explanation:<\/b><\/p>\n

          Endpoint Firewall rules are enforced from the top of the rule base to the bottom. Rule priority therefore matters because the first matching rule determines how the traffic is handled. More specific rules should generally be placed above broader rules when the specific behavior needs to take precedence. Check Point notes that the final rule is commonly a Cleanup Rule that blocks traffic not matched by earlier allow rules. Understanding rule order is essential when troubleshooting traffic that appears unexpectedly permitted or denied.<\/span><\/p>\n

          Question 185. What is usually the last Firewall rule?<\/b><\/p>\n

            \n
          1. <\/b> Stealth Rule<\/span><\/li>\n
          2. <\/b> DHCP Rule<\/span><\/li>\n
          3. <\/b> VPN Rule<\/span><\/li>\n
          4. <\/b> Cleanup Rule<\/span><\/li>\n<\/ol>\n

            Correct Answer: 4. Cleanup Rule<\/b><\/p>\n

            Explanation:<\/b><\/p>\n

            A Cleanup Rule is commonly placed at the bottom of the Firewall rule base. Its purpose is to block traffic that has not matched any earlier explicit allow rule. This provides a default-deny approach rather than permitting unexpected connections simply because no specific rule addressed them. Check Point’s Endpoint Firewall documentation states that rules are processed in sequence and that the last rule is usually a Cleanup Rule that drops unmatched traffic. Logging the cleanup action can also help administrators identify connections that require additional policy review.<\/span><\/p>\n

            Question 186. What does the Trusted Zone contain?<\/b><\/p>\n

              \n
            1. <\/b> Trusted network objects<\/span><\/li>\n
            2. <\/b> Malware samples<\/span><\/li>\n
            3. <\/b> Quarantined files<\/span><\/li>\n
            4. <\/b> Encryption keys<\/span><\/li>\n<\/ol>\n

              Correct Answer: 1. Trusted network objects<\/b><\/p>\n

              Explanation:<\/b><\/p>\n

              The Trusted Zone contains network objects that the organization considers trusted for Endpoint Firewall purposes. Administrators should include only those network objects with which protected programs and endpoints legitimately need to interact. Examples can include corporate networks, DNS servers, domain controllers, file servers, management servers, and other approved infrastructure. Objects not included in the Trusted Zone are automatically treated as belonging to the Internet Zone. Careful Trusted Zone design helps distinguish corporate resources from less trusted network locations.<\/span><\/p>\n

              Question 187. Where do objects outside the Trusted Zone go?<\/b><\/p>\n

                \n
              1. <\/b> Quarantine Zone<\/span><\/li>\n
              2. <\/b> DMZ Zone<\/span><\/li>\n
              3. <\/b> Internet Zone<\/span><\/li>\n
              4. <\/b> Management Zone<\/span><\/li>\n<\/ol>\n

                Correct Answer: 3. Internet Zone<\/b><\/p>\n

                Explanation:<\/b><\/p>\n

                Any network object that is not part of the Trusted Zone is automatically considered part of the Internet Zone. This simplifies policy construction because administrators do not need to manually enumerate every untrusted external network. The firewall can apply more permissive controls to trusted corporate resources and more restrictive controls to everything else. Access Zones therefore provide a logical security classification that Firewall rules can reference when deciding how inbound and outbound traffic should be handled.<\/span><\/p>\n

                Question 188. How many Trusted Zones can one device enforce?<\/b><\/p>\n

                  \n
                1. <\/b> Unlimited<\/span><\/li>\n
                2. <\/b> One<\/span><\/li>\n
                3. <\/b> Two<\/span><\/li>\n
                4. <\/b> Four<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 2. One<\/b><\/p>\n

                  Explanation:<\/b><\/p>\n

                  A device can enforce only one Trusted Zone at a time. If multiple policy rules apply to the same endpoint and more than one Trusted Zone could be selected, only the last applicable Trusted Zone is enforced. Administrators should therefore design Access Zones carefully and understand policy order so the endpoint receives the intended trusted-network definition. This restriction helps keep the effective security-zone configuration unambiguous on each managed device.<\/span><\/p>\n

                  Question 189. Which address must always remain accessible locally?<\/b><\/p>\n

                    \n
                  1. <\/b> 127.0.0.1<\/span><\/li>\n
                  2. <\/b> 8.8.8.8<\/span><\/li>\n
                  3. <\/b> 255.255.255.255<\/span><\/li>\n
                  4. <\/b> 169.254.1.1<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. 127.0.0.1<\/b><\/p>\n

                    Explanation:<\/b><\/p>\n

                    The endpoint must always have access to its local loopback address, 127.0.0.1. Check Point defines the LocalMachine_Loopback network object for this purpose and includes it in the initial Trusted Zone configuration. Local applications often use the loopback interface to communicate with services running on the same device. Check Point also warns against software that changes or hides the local loopback address, such as some personal proxy tools, because such behavior can interfere with expected endpoint networking.<\/span><\/p>\n

                    Question 190. What does <\/b>All_Internet<\/b> represent?<\/b><\/p>\n

                      \n
                    1. <\/b> Only private IP addresses<\/span><\/li>\n
                    2. <\/b> Only corporate WANs<\/span><\/li>\n
                    3. <\/b> Loopback addresses<\/span><\/li>\n
                    4. <\/b> All legal IP addresses<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4. All legal IP addresses<\/b><\/p>\n

                      Explanation:<\/b><\/p>\n

                      The <\/span>All_Internet<\/span> object represents all legal IP addresses. It appears in the initial Access Zones configuration along with LocalMachine_Loopback. Check Point notes that having <\/span>All_Internet<\/span> in the initial Trusted Zone does not by itself mean all internet traffic is automatically permitted, because Access Zones are used as components of Firewall policy rather than functioning as an independently enforced allow policy. Administrators should evaluate and customize zone membership before relying on it for production security decisions.<\/span><\/p>\n

                      Question 191. Which object can belong to a Trusted Zone?<\/b><\/p>\n

                        \n
                      1. <\/b> Malware hash<\/span><\/li>\n
                      2. <\/b> Network Group<\/span><\/li>\n
                      3. <\/b> Encryption user<\/span><\/li>\n
                      4. <\/b> Threat report<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 2. Network Group<\/b><\/p>\n

                        Explanation:<\/b><\/p>\n

                        Network Groups are among the supported object types that can be placed in a Trusted Zone. Other supported types include hosts, networks, domains, and address ranges. This gives administrators flexibility when describing trusted portions of the infrastructure. For example, several related corporate networks can be placed into a Network Group and then added to the Trusted Zone as one logical object. Using structured objects simplifies policy maintenance compared with repeatedly entering individual IP addresses.<\/span><\/p>\n

                        Question 192. What identifies an Endpoint Firewall service?<\/b><\/p>\n

                          \n
                        1. <\/b> Username only<\/span><\/li>\n
                        2. <\/b> File hash<\/span><\/li>\n
                        3. <\/b> Protocol, port, and signature<\/span><\/li>\n
                        4. <\/b> Disk volume<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. Protocol, port, and signature<\/b><\/p>\n

                          Explanation:<\/b><\/p>\n

                          Endpoint Firewall services are matched according to network characteristics such as IP protocol, TCP or UDP port number, and protocol signature. Service objects let administrators describe network communication patterns in a reusable way and reference them in firewall rules. For example, rules can permit a required application protocol while blocking unrelated traffic. Service Groups can combine multiple service objects when several protocols should receive the same policy treatment.<\/span><\/p>\n

                          Question 193. Why is rule priority important?<\/b><\/p>\n

                            \n
                          1. <\/b> Rules are processed sequentially<\/span><\/li>\n
                          2. <\/b> It changes encryption strength<\/span><\/li>\n
                          3. <\/b> It updates malware signatures<\/span><\/li>\n
                          4. <\/b> It controls licenses<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. Rules are processed sequentially<\/b><\/p>\n

                            Explanation:<\/b><\/p>\n

                            Rule priority matters because Endpoint Firewall evaluates rules according to their sequence in the rule base. A rule near the top can match traffic before a broader rule lower in the policy is reached. Administrators should therefore place specific exceptions and required access rules in positions that produce the desired behavior. When traffic is unexpectedly blocked or allowed, reviewing rule sequence is one of the first troubleshooting steps. The Cleanup Rule is normally kept at the end so unmatched traffic is denied after all intentional exceptions are considered.<\/span><\/p>\n

                            Question 194. Which traffic can the default inbound action permit?<\/b><\/p>\n

                              \n
                            1. <\/b> Only DNS<\/span><\/li>\n
                            2. <\/b> Only SMTP<\/span><\/li>\n
                            3. <\/b> Only HTTPS<\/span><\/li>\n
                            4. <\/b> Trusted-zone and connectivity traffic<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 4. Trusted-zone and connectivity traffic<\/b><\/p>\n

                              Explanation:<\/b><\/p>\n

                              One available inbound action automatically permits traffic from trusted zones together with required connectivity services while blocking other inbound traffic. Check Point documentation identifies IP-obtaining traffic such as DHCP-related services among the automatically generated inbound rules. Administrators can inspect and customize the resulting rule base when additional inbound services are required. This provides a safer default than accepting every incoming connection while still permitting essential endpoint connectivity and approved trusted-network communication.<\/span><\/p>\n

                              Question 195. Why is DHCP allowed in the default inbound rule base?<\/b><\/p>\n

                                \n
                              1. <\/b> For disk encryption<\/span><\/li>\n
                              2. <\/b> To obtain network configuration<\/span><\/li>\n
                              3. <\/b> To scan applications<\/span><\/li>\n
                              4. <\/b> To create logs<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 2. To obtain network configuration<\/b><\/p>\n

                                Explanation:<\/b><\/p>\n

                                DHCP-related traffic is permitted in the default inbound configuration so an endpoint can obtain necessary network parameters such as an IP address. Check Point’s default inbound rule examples include BOOTP and DHCP request, reply, and relay-related services under the IP-obtaining rule. Without this connectivity, a device could be unable to establish normal network communication after joining a network. Firewall policy must therefore distinguish essential infrastructure traffic from unnecessary inbound connections.<\/span><\/p>\n

                                Question 196. What is absent from the classic inbound Rule Base?<\/b><\/p>\n

                                  \n
                                1. <\/b> Action column<\/span><\/li>\n
                                2. <\/b> Source column<\/span><\/li>\n
                                3. <\/b> Destination column<\/span><\/li>\n
                                4. <\/b> Service column<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. Destination column<\/b><\/p>\n

                                  Explanation:<\/b><\/p>\n

                                  The classic R81.20 Endpoint inbound Rule Base does not include a destination column because the destination of all inbound traffic is the endpoint computer itself. Administrators instead define the source, service, action, tracking behavior, and other relevant rule properties. This simplifies the endpoint-specific inbound policy model compared with a gateway rule base where both source and destination can vary widely. Knowing this design also helps candidates distinguish inbound endpoint firewall rules from outbound rules.<\/span><\/p>\n

                                  Question 197. What is absent from the classic outbound Rule Base?<\/b><\/p>\n

                                    \n
                                  1. <\/b> Source column<\/span><\/li>\n
                                  2. <\/b> Destination column<\/span><\/li>\n
                                  3. <\/b> Action column<\/span><\/li>\n
                                  4. <\/b> Service column<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. Source column<\/b><\/p>\n

                                    Explanation:<\/b><\/p>\n

                                    In the classic outbound Rule Base, the source is always the local endpoint computer, so a separate source column is not required. Administrators mainly define destinations, services, actions, and other rule properties for traffic leaving the protected device. This mirrors the inbound model, where the destination is implicitly the endpoint. Understanding this distinction makes it easier to build and troubleshoot rules in the correct direction.<\/span><\/p>\n

                                    Question 198. When does domain-object DNS resolution occur?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Every packet<\/span><\/li>\n
                                    2. <\/b> Every minute<\/span><\/li>\n
                                    3. <\/b> Every heartbeat<\/span><\/li>\n
                                    4. <\/b> At policy application or reboot<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 3. At policy application or reboot<\/b><\/p>\n

                                      Explanation:<\/b><\/p>\n

                                      For Endpoint Firewall domain objects, Check Point documents that DNS resolution occurs when the policy is applied or after the endpoint reboots. It is not continuously resolved for every packet or heartbeat. Administrators should understand this behavior when firewall rules depend on FQDN-based objects, because DNS changes may not be reflected immediately on an endpoint until the next supported resolution event. Sub-sites also need to be defined separately, and wildcard characters are not supported for these domain objects.<\/span><\/p>\n

                                      Question 199. Are wildcard characters supported in Firewall domain objects?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Always<\/span><\/li>\n
                                      2. <\/b> Only <\/span>*<\/span><\/li>\n
                                      3. <\/b> No<\/span><\/li>\n
                                      4. <\/b> Only <\/span>?<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 4. No<\/b><\/p>\n

                                        Explanation:<\/b><\/p>\n

                                        Wildcard symbols such as <\/span>*<\/span> are not supported when defining Endpoint Firewall domain objects in the referenced R81.20 web-management documentation. Administrators must use a fully qualified domain name, and sub-sites that require separate handling need to be added individually. Non-qualified domain names are also unsupported. These restrictions are important when building domain-based rules because administrators cannot assume one wildcard domain object will automatically cover every subdomain.<\/span><\/p>\n

                                        Question 200. What should happen after changing Firewall rules?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Install Policy<\/span><\/li>\n
                                        2. <\/b> Reformat the endpoint<\/span><\/li>\n
                                        3. <\/b> Recreate the tenant<\/span><\/li>\n
                                        4. <\/b> Run Appscan<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 2. Install Policy<\/b><\/p>\n

                                          Explanation:<\/b><\/p>\n

                                          After Firewall rule changes are saved, the updated policy must be installed so managed endpoints receive and enforce the new configuration. Editing a rule in the management console alone does not complete enforcement. Check Point’s Firewall management procedure explicitly includes saving the changes and then clicking Install Policy above the rule base. This is an important troubleshooting point when an administrator changes a firewall rule but endpoint behavior remains unchanged.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Checkpoint 156-536 Exam Dumps and Practice Test Dumps. Question 181. What does Endpoint Firewall control? Disk encryption Network traffic Malware signatures Application inventory Correct Answer: 2. Network traffic Explanation: Harmony Endpoint Firewall controls network traffic entering and leaving managed endpoint computers. Rules can make decisions based on connection details such as IP addresses, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21599"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=21599"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21599\/revisions"}],"predecessor-version":[{"id":21600,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21599\/revisions\/21600"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}