{"id":21494,"date":"2026-09-25T05:30:32","date_gmt":"2026-09-25T05:30:32","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21494"},"modified":"2026-09-25T05:30:32","modified_gmt":"2026-09-25T05:30:32","slug":"hp-hpe6-a85-practice-test-questions-and-exam-dumps-part18-q341-360","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/hp-hpe6-a85-practice-test-questions-and-exam-dumps-part18-q341-360\/","title":{"rendered":"HP HPE6-A85 Practice Test Questions and Exam Dumps Part18 Q341-360"},"content":{"rendered":"

View Full <\/b>HP HPE6-A85 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/p>\n


\n<\/b>Question 341. What does port security control?<\/b><\/p>\n

    \n
  1. <\/b> OSPF routes<\/span><\/li>\n
  2. <\/b> Authorized MAC addresses<\/span><\/li>\n
  3. <\/b> AP channels<\/span><\/li>\n
  4. <\/b> NTP servers<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. Authorized MAC addresses<\/b><\/p>\n

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

    Port security controls which endpoint MAC addresses are authorized to communicate through a switch port. AOS-CX can use static, dynamically learned, or sticky MAC addresses depending on configuration. When unauthorized devices attempt to use a protected interface, the switch can detect, prevent, and log the activity. This makes port security useful on access ports where administrators know which endpoints should normally be connected. It does not protect routing protocols, WLAN radio channels, or time synchronization.<\/span><\/p>\n

    Question 342. What is the default port-security learning mode?<\/b><\/p>\n

      \n
    1. <\/b> Sticky only<\/span><\/li>\n
    2. <\/b> Static only<\/span><\/li>\n
    3. <\/b> Disabled permanently<\/span><\/li>\n
    4. <\/b> Dynamic<\/span><\/li>\n<\/ol>\n

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

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

      HPE documents the default port-security behavior as dynamic mode, in which the switch learns MAC addresses from inbound traffic from connected devices. Administrators can later restrict the port by configuring static authorized MAC addresses, a client limit, or sticky learning. Dynamic learning is convenient initially because the switch does not require every endpoint MAC address to be entered manually. However, stronger restrictions may be appropriate on sensitive access ports where only known devices should be permitted.<\/span><\/p>\n

      Question 343. What does sticky learning do?<\/b><\/p>\n

        \n
      1. <\/b> Retains learned MAC addresses<\/span><\/li>\n
      2. <\/b> Deletes all MAC addresses<\/span><\/li>\n
      3. <\/b> Disables port security<\/span><\/li>\n
      4. <\/b> Enables LACP<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. Retains learned MAC addresses<\/b><\/p>\n

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

        Sticky learning converts existing and newly learned non-static MAC addresses into sticky MAC entries on a protected port. HPE states that sticky authorized clients can remain recognized through events such as switch reboots or link flaps after being learned. This allows administrators to learn legitimate endpoints dynamically and then retain those bindings without manually entering every MAC address. If sticky learning is later disabled, the sticky entries become dynamic clients again. Sticky learning is therefore a port-security persistence feature, not an LACP or VLAN mechanism.<\/span><\/p>\n

        Question 344. What happens if a sticky MAC moves ports?<\/b><\/p>\n

          \n
        1. <\/b> Nothing<\/span><\/li>\n
        2. <\/b> It becomes a route<\/span><\/li>\n
        3. <\/b> A violation occurs<\/span><\/li>\n
        4. <\/b> It becomes multicast<\/span><\/li>\n<\/ol>\n

          Correct Answer: 3. A violation occurs<\/b><\/p>\n

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

          A sticky MAC is associated with the port on which it was learned or configured. HPE documents that moving a sticky MAC client from one port to another is treated as a security violation. The switch can record the event, and administrators can display sticky-MAC move violations with the appropriate port-security diagnostic command. This helps prevent an authorized device identity from being moved to another access port without detection and can reduce the risk of station movement or MAC hijacking.<\/span><\/p>\n

          Question 345. What does <\/b>client-limit<\/b> set?<\/b><\/p>\n

            \n
          1. <\/b> Maximum VLANs<\/span><\/li>\n
          2. <\/b> Maximum routes<\/span><\/li>\n
          3. <\/b> Maximum LAG members<\/span><\/li>\n
          4. <\/b> Maximum clients on a port<\/span><\/li>\n<\/ol>\n

            Correct Answer: 4. Maximum clients on a port<\/b><\/p>\n

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

            The port-security <\/span>client-limit<\/span> setting defines the maximum number of clients that may be authorized or learned on a protected interface. HPE documents a default value of one client, with supported maximum values depending on the switch platform. Client MAC addresses can be entered statically, learned dynamically, or managed using a combination of both. If the configured limit is exceeded, the switch can trigger the configured security-violation behavior. This is useful on ports where only a known number of endpoints should be connected.<\/span><\/p>\n

            Question 346. What is the default violation action?<\/b><\/p>\n

              \n
            1. <\/b> Notify<\/span><\/li>\n
            2. <\/b> Reboot<\/span><\/li>\n
            3. <\/b> Shutdown<\/span><\/li>\n
            4. <\/b> Ignore<\/span><\/li>\n<\/ol>\n

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

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

              HPE documents notify as the default action when a port-access security violation occurs. In this mode, the switch records the violation as an event or syslog message and can also send an SNMP trap notification. The port itself is not automatically shut down simply because the default notify action is used. Administrators who want a stronger enforcement response can configure the shutdown action instead. Choosing between notification and shutdown depends on the security requirement and the acceptable operational impact of disabling a production access port.<\/span><\/p>\n

              Question 347. What does violation action <\/b>shutdown<\/b> do?<\/b><\/p>\n

                \n
              1. <\/b> Sends only a log<\/span><\/li>\n
              2. <\/b> Shuts the affected port<\/span><\/li>\n
              3. <\/b> Deletes the VLAN<\/span><\/li>\n
              4. <\/b> Reboots the switch<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. Shuts the affected port<\/b><\/p>\n

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

                When the security-violation action is configured as shutdown, AOS-CX shuts down the affected port after the relevant violation occurs, such as exceeding the configured client limit. This is a more disruptive but stronger security response than the default notify action. HPE also supports optional automatic recovery so a port disabled by a security violation can later return to service after the configured recovery period. Administrators should use shutdown carefully because it can interrupt legitimate users if client limits or policy are configured incorrectly.<\/span><\/p>\n

                Question 348. What does shutdown auto-recovery provide?<\/b><\/p>\n

                  \n
                1. <\/b> New firmware<\/span><\/li>\n
                2. <\/b> VLAN recovery<\/span><\/li>\n
                3. <\/b> Automatic port restoration<\/span><\/li>\n
                4. <\/b> AP failover<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. Automatic port restoration<\/b><\/p>\n

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

                  Automatic recovery allows an interface that was shut down by a port-access security violation to return to service after a defined recovery period. Without auto-recovery, an administrator may need to intervene manually before normal operation resumes. HPE provides commands for enabling shutdown auto-recovery and defining the associated recovery timer. This feature balances enforcement and availability: a violation can immediately disable the affected port while still allowing the network to restore service automatically after the configured delay.<\/span><\/p>\n

                  Question 349. What does <\/b>client-status<\/b> show?<\/b><\/p>\n

                    \n
                  1. <\/b> Authorized port-security clients<\/span><\/li>\n
                  2. <\/b> OSPF neighbors<\/span><\/li>\n
                  3. <\/b> PoE budgets<\/span><\/li>\n
                  4. <\/b> NTP peers<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. Authorized port-security clients<\/b><\/p>\n

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

                    The port-security <\/span>client-status<\/span> display shows authorized clients associated with protected switch ports. HPE output can identify client MAC addresses and whether each client is static, dynamic, sticky-static, or sticky-dynamic. Administrators can filter the output by interface or, on supported platforms, by MAC address. This makes the command useful when troubleshooting why a particular endpoint is permitted or rejected on an access port. It provides port-security information rather than routing, power, or time-synchronization status.<\/span><\/p>\n

                    Question 350. What does <\/b>port-statistics<\/b> show?<\/b><\/p>\n

                      \n
                    1. <\/b> OSPF cost<\/span><\/li>\n
                    2. <\/b> RF utilization<\/span><\/li>\n
                    3. <\/b> DHCP options<\/span><\/li>\n
                    4. <\/b> Port-security client counts<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4. Port-security client counts<\/b><\/p>\n

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

                      The port-security <\/span>port-statistics<\/span> command displays client statistics for protected interfaces. HPE examples include the number of authorized clients and the number of sticky authorized clients associated with each port. Administrators can display statistics for all interfaces or filter the output to a specific port. These statistics help verify whether the expected number of devices has been authorized and whether sticky learning is operating as intended. The command is specifically focused on port-security state rather than WLAN, routing, or DHCP configuration.<\/span><\/p>\n

                      Question 351. What does MAC Lockdown do?<\/b><\/p>\n

                        \n
                      1. <\/b> Enables DHCP relay<\/span><\/li>\n
                      2. <\/b> Increases MTU<\/span><\/li>\n
                      3. <\/b> Binds a MAC to a port<\/span><\/li>\n
                      4. <\/b> Creates a VRF<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 3. Binds a MAC to a port<\/b><\/p>\n

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

                        MAC Lockdown, also called Static Addressing, prevents a station from moving freely between switch ports by allowing the configured MAC address to use only its assigned interface. HPE also notes that MAC Lockdown restricts the device to a specific VLAN. This helps protect against station movement and certain MAC hijacking scenarios. MAC Lockdown is more restrictive than ordinary dynamic learning and should therefore be used where endpoint placement is expected to remain stable. It is unrelated to DHCP relay, interface MTU, or VRF configuration.<\/span><\/p>\n

                        Question 352. Which has higher priority?<\/b><\/p>\n

                          \n
                        1. <\/b> Dynamic learning<\/span><\/li>\n
                        2. <\/b> MAC Lockdown<\/span><\/li>\n
                        3. <\/b> LLDP<\/span><\/li>\n
                        4. <\/b> DHCP snooping<\/span><\/li>\n<\/ol>\n

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

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

                          HPE explicitly states that MAC Lockdown has higher priority than port security. MAC Lockdown creates a strong static association between a device MAC address, its allowed switch port, and its VLAN. If overlapping access controls exist, administrators should understand this priority because it affects which mechanism governs the endpoint. The feature is useful where station movement must be prevented. Dynamic MAC learning and DHCP snooping serve different purposes and do not supersede the configured MAC Lockdown relationship.<\/span><\/p>\n

                          Question 353. What does port security NOT block by itself?<\/b><\/p>\n

                            \n
                          1. <\/b> Static clients<\/span><\/li>\n
                          2. <\/b> Sticky clients<\/span><\/li>\n
                          3. <\/b> Unauthorized unicast<\/span><\/li>\n
                          4. <\/b> Received broadcast and multicast<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 4. Received broadcast and multicast<\/b><\/p>\n

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

                            HPE documents an important limitation: port security does not prevent an intruder from receiving broadcast and multicast traffic. Port security primarily restricts whether unauthorized source MAC addresses can communicate through the switch port. Broadcast and multicast frames may still be received because those traffic types are distributed differently from known unicast traffic. Additional segmentation and access controls may therefore be required when protecting sensitive information from unauthorized endpoints. Port security should be viewed as one security layer rather than a complete endpoint-isolation mechanism.<\/span><\/p>\n

                            Question 354. Can MAC authentication and port security share one port?<\/b><\/p>\n

                              \n
                            1. <\/b> Always<\/span><\/li>\n
                            2. <\/b> No, they are mutually exclusive<\/span><\/li>\n
                            3. <\/b> Only with OSPF<\/span><\/li>\n
                            4. <\/b> Only on trunks<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2. No, they are mutually exclusive<\/b><\/p>\n

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

                              HPE documents that MAC authentication and port security are mutually exclusive on a given port on the applicable AOS-CX platforms. MAC authentication uses the client MAC address as an identity input for RADIUS-based authentication, while port security maintains its own authorized MAC behavior. Because these functions overlap in endpoint admission control, administrators should select the appropriate mechanism instead of attempting to enable both simultaneously on the same port. The same documentation also notes other feature interactions that should be reviewed before configuring port access.<\/span><\/p>\n

                              Question 355. What does LACP fallback-static allow?<\/b><\/p>\n

                                \n
                              1. <\/b> One member to forward without an LACP partner<\/span><\/li>\n
                              2. <\/b> All members to forward independently<\/span><\/li>\n
                              3. <\/b> Automatic VSF creation<\/span><\/li>\n
                              4. <\/b> VLAN deletion<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1. One member to forward without an LACP partner<\/b><\/p>\n

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

                                LACP fallback-static provides temporary connectivity when an LACP-enabled LAG does not detect an LACP partner. HPE documents that one member interface is selected to remain up and forward traffic, while the other members remain in an LACP-blocked state. This can be useful during server boot or provisioning when the remote endpoint is not yet running LACP. Allowing multiple independent links to forward would create risks such as loops and MAC-learning problems, so fallback intentionally permits only one active member.<\/span><\/p>\n

                                Question 356. Without LACP fallback, what happens with no partner?<\/b><\/p>\n

                                  \n
                                1. <\/b> All members forward<\/span><\/li>\n
                                2. <\/b> One random VLAN forwards<\/span><\/li>\n
                                3. <\/b> The LAG blocks<\/span><\/li>\n
                                4. <\/b> The switch reboots<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. The LAG blocks<\/b><\/p>\n

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

                                  HPE states that when LACP fallback-static is not enabled and no LACP partner is detected, the LAG enters a BLOCK state. This prevents traffic from being forwarded incorrectly over links that have not successfully negotiated an aggregation relationship. Enabling fallback-static changes that behavior by allowing exactly one physical member to forward temporarily. Administrators should use fallback only where required and should still expect normal LACP negotiation to take over when the peer begins participating correctly.<\/span><\/p>\n

                                  Question 357. What does broadcast rate limiting control?<\/b><\/p>\n

                                    \n
                                  1. <\/b> Egress routing<\/span><\/li>\n
                                  2. <\/b> Ingress broadcast traffic<\/span><\/li>\n
                                  3. <\/b> AP association<\/span><\/li>\n
                                  4. <\/b> NTP polling<\/span><\/li>\n<\/ol>\n

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

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

                                    The AOS-CX <\/span>rate-limit broadcast<\/span> function limits the amount of broadcast traffic entering an Ethernet interface. This can help reduce the effect of broadcast storms or abnormal endpoint behavior that could otherwise consume excessive bandwidth and processing resources. HPE also provides rate limiting for traffic categories such as multicast, unknown unicast, and ICMP on supported platforms. Rate limiting should be configured carefully because thresholds that are too low can discard legitimate traffic needed for normal network operation.<\/span><\/p>\n

                                    Question 358. Which rate-limit units are supported?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Mbps only<\/span><\/li>\n
                                    2. <\/b> Frames only<\/span><\/li>\n
                                    3. <\/b> Seconds only<\/span><\/li>\n
                                    4. <\/b> kbps, percent, or pps<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 4. kbps, percent, or pps<\/b><\/p>\n

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

                                      HPE documents several supported ways to express AOS-CX interface rate limits: kilobits per second (kbps), percentage of link bandwidth, or packets per second (pps). This provides flexibility when configuring traffic controls. A fixed kbps rate may be useful when a precise bandwidth limit is required, percent scales relative to interface speed, and pps can be useful for traffic types where packet rate is the concern. The actual applied rate can be inspected with interface QoS commands on supported switches.<\/span><\/p>\n

                                      Question 359. How is a LAG rate limit applied?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Once to the whole LAG<\/span><\/li>\n
                                      2. <\/b> Only to the first link<\/span><\/li>\n
                                      3. <\/b> Separately to each member<\/span><\/li>\n
                                      4. <\/b> Only when LACP fails<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3. Separately to each member<\/b><\/p>\n

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

                                        HPE documents that applicable ingress rate limits on a LAG are enforced separately on each individual member interface, rather than as one aggregate limit across the entire logical LAG. This distinction matters when calculating how much traffic can enter a bundle. For example, a rate applied to a LAG with several active physical members can effectively be enforced independently on each link. Administrators should account for this behavior when designing broadcast, multicast, unknown-unicast, or ICMP protection policies.<\/span><\/p>\n

                                        Question 360. Which design BEST protects an access port?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Port security, sticky MAC, limits, and violation actions<\/span><\/li>\n
                                        2. <\/b> Disable all security<\/span><\/li>\n
                                        3. <\/b> Allow unlimited clients<\/span><\/li>\n
                                        4. <\/b> Trust every MAC dynamically<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 1. Port security, sticky MAC, limits, and violation actions<\/b><\/p>\n

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

                                          A well-protected access port can combine several AOS-CX controls. Port security restricts authorized endpoint MAC addresses. Sticky learning can retain legitimate dynamically learned clients. A client limit prevents an unexpected number of devices from using the port, while violation actions determine whether unauthorized behavior generates notifications or shuts the interface down. Traffic rate limiting can provide an additional layer against excessive broadcast or similar traffic where appropriate. Together, these controls offer stronger endpoint protection than unlimited dynamic learning with no enforcement or monitoring.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full HP HPE6-A85 Exam Dumps and Practice Test Dumps. Question 341. What does port security control? OSPF routes Authorized MAC addresses AP channels NTP servers Correct Answer: 2. Authorized MAC addresses Explanation: Port security controls which endpoint MAC addresses are authorized to communicate through a switch port. AOS-CX can use static, dynamically learned, or […]<\/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\/21494"}],"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=21494"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21494\/revisions"}],"predecessor-version":[{"id":21495,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21494\/revisions\/21495"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}