{"id":21470,"date":"2026-09-25T05:26:56","date_gmt":"2026-09-25T05:26:56","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21470"},"modified":"2026-09-25T05:26:56","modified_gmt":"2026-09-25T05:26:56","slug":"hp-hpe6-a85-practice-test-questions-and-exam-dumps-part6-q101-120","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/hp-hpe6-a85-practice-test-questions-and-exam-dumps-part6-q101-120\/","title":{"rendered":"HP HPE6-A85 Practice Test Questions and Exam Dumps Part6 Q101-120"},"content":{"rendered":"

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


\n<\/b>Question 101. On an AOS-CX switch, what is the PRIMARY purpose of configuring an interface as an access port?<\/b><\/p>\n

    \n
  1. <\/b> To carry every VLAN configured on the switch<\/span><\/li>\n
  2. <\/b> To associate ordinary untagged endpoint traffic with a single access VLAN<\/span><\/li>\n
  3. <\/b> To establish an LACP bundle automatically<\/span><\/li>\n
  4. <\/b> To enable Layer 3 routing on the interface<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. To associate ordinary untagged endpoint traffic with a single access VLAN<\/b><\/p>\n

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

    An access port is normally used for endpoints such as PCs, printers, cameras, or other devices that belong to one VLAN. The switch associates untagged traffic arriving on the interface with the configured access VLAN and forwards traffic according to that VLAN’s Layer 2 forwarding domain. This differs from a trunk interface, which is designed to transport multiple VLANs across a single physical or logical link. Current HPE Aruba Networking Central switch profiles distinguish Access and Trunk VLAN modes and allow administrators to assign the appropriate VLAN behavior to an interface.<\/span><\/p>\n

    Question 102. What is the PRIMARY purpose of an AOS-CX trunk interface?<\/b><\/p>\n

      \n
    1. <\/b> To support only one untagged user VLAN<\/span><\/li>\n
    2. <\/b> To disable VLAN tagging<\/span><\/li>\n
    3. <\/b> To operate only as a routed interface<\/span><\/li>\n
    4. <\/b> To carry traffic for multiple VLANs across one link<\/span><\/li>\n<\/ol>\n

      Correct Answer: 4. To carry traffic for multiple VLANs across one link<\/b><\/p>\n

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

      A trunk interface is used when several VLANs must traverse the same physical or logical connection, such as an uplink between switches. HPE Aruba Networking Central distinguishes trunk mode from access mode: an access port carries traffic for its assigned access VLAN, while a trunk can carry multiple permitted VLANs. Administrators should allow only the VLANs that are actually required across the trunk rather than unnecessarily exposing every VLAN. Correct trunk configuration is essential for maintaining Layer 2 segmentation across a campus network.<\/span><\/p>\n

      Question 103. What does the native VLAN on an AOS-CX trunk primarily identify?<\/b><\/p>\n

        \n
      1. <\/b> The VLAN associated with untagged traffic on that trunk<\/span><\/li>\n
      2. <\/b> The VLAN used exclusively for spanning-tree BPDUs<\/span><\/li>\n
      3. <\/b> The VLAN containing every routed interface<\/span><\/li>\n
      4. <\/b> The VLAN that automatically receives the highest QoS priority<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. The VLAN associated with untagged traffic on that trunk<\/b><\/p>\n

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

        A trunk can carry several VLANs, normally using VLAN tags to distinguish them. The native VLAN provides the VLAN association for untagged traffic on the trunk. HPE configuration examples show trunk interfaces with both a configured native VLAN and an allowed-VLAN list. Administrators should ensure that native VLAN configuration is consistent across both ends of the link because mismatches can place untagged traffic into different Layer 2 domains and produce difficult-to-diagnose connectivity or security problems. The native VLAN is not inherently a management or priority VLAN.<\/span><\/p>\n

        Question 104. What is the PRIMARY function of the allowed-VLAN list on a trunk?<\/b><\/p>\n

          \n
        1. <\/b> To determine which routing protocols can use the interface<\/span><\/li>\n
        2. <\/b> To select the LACP system priority<\/span><\/li>\n
        3. <\/b> To limit which VLANs are permitted to traverse the trunk<\/span><\/li>\n
        4. <\/b> To identify DHCP servers<\/span><\/li>\n<\/ol>\n

          Correct Answer: 3. To limit which VLANs are permitted to traverse the trunk<\/b><\/p>\n

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

          The allowed-VLAN list defines which VLANs may be carried across a trunk interface. This prevents unrelated VLANs from propagating over uplinks where they are not needed. HPE specifically warns against unrestricted VLAN propagation on access-switch uplinks because unnecessary VLANs may permit unintended traffic to enter parts of the access layer. A well-designed campus therefore permits only the VLANs required by the topology and services on each trunk. This improves segmentation, reduces unnecessary Layer 2 propagation, and simplifies troubleshooting.<\/span><\/p>\n

          Question 105. What is the PRIMARY purpose of a Link Aggregation Group (LAG)?<\/b><\/p>\n

            \n
          1. <\/b> To create multiple independent spanning-tree roots<\/span><\/li>\n
          2. <\/b> To combine several physical links into one logical interface for bandwidth and redundancy<\/span><\/li>\n
          3. <\/b> To replace VLANs with routed ports<\/span><\/li>\n
          4. <\/b> To authenticate users with RADIUS<\/span><\/li>\n<\/ol>\n

            Correct Answer: 2. To combine several physical links into one logical interface for bandwidth and redundancy<\/b><\/p>\n

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

            A LAG groups multiple physical Ethernet interfaces into one logical link. This can increase aggregate bandwidth while also providing redundancy if one member link fails. To upper-layer protocols and many switching functions, the group behaves as one logical interface. HPE Aruba Networking Central supports static LAGs as well as LACP-based LAGs. LAGs are commonly used for switch uplinks, server connections, and other links that require both capacity and resiliency. Traffic is distributed across members according to the platform’s hashing behavior rather than simply duplicated across all links.<\/span><\/p>\n

            Question 106. What does LACP Active mode do?<\/b><\/p>\n

              \n
            1. <\/b> It actively initiates LACP negotiation by sending LACPDUs<\/span><\/li>\n
            2. <\/b> It waits indefinitely for the remote side and never sends LACPDUs<\/span><\/li>\n
            3. <\/b> It disables link-failure detection<\/span><\/li>\n
            4. <\/b> It converts the LAG into a routed interface automatically<\/span><\/li>\n<\/ol>\n

              Correct Answer: 1. It actively initiates LACP negotiation by sending LACPDUs<\/b><\/p>\n

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

              When LACP operates in Active mode, the interface actively sends Link Aggregation Control Protocol Data Units to establish and maintain the aggregation relationship. HPE documentation contrasts this with Passive mode, where the local side waits for the remote device to initiate negotiation. At least one side normally needs to operate in Active mode for dynamic LACP negotiation to start successfully. Using LACP gives the devices signaling information about the bundle and helps detect certain configuration and member-link problems that a purely static LAG cannot detect through protocol exchange.<\/span><\/p>\n

              Question 107. What happens if both ends of an LACP connection are configured as Passive?<\/b><\/p>\n

                \n
              1. <\/b> The links automatically become routed interfaces<\/span><\/li>\n
              2. <\/b> The bundle becomes a static LAG<\/span><\/li>\n
              3. <\/b> Both sides immediately transmit LACPDUs<\/span><\/li>\n
              4. <\/b> Neither side initiates LACP negotiation, so the dynamic LAG does not form normally<\/span><\/li>\n<\/ol>\n

                Correct Answer: 4. Neither side initiates LACP negotiation, so the dynamic LAG does not form normally<\/b><\/p>\n

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

                LACP Passive mode waits for the peer to initiate the LACP exchange. If both sides are Passive, neither side begins sending the required negotiation messages, so the dynamic LAG does not establish as intended. HPE Aruba Networking Central documentation specifically notes that Active mode initiates the LACP connection, whereas Passive waits for the remote side. A common troubleshooting step for a LAG that fails to form is therefore to confirm that at least one endpoint is configured for Active mode and that member interfaces have compatible parameters.<\/span><\/p>\n

                Question 108. What is a key disadvantage of a static LAG compared with an LACP-based LAG?<\/b><\/p>\n

                  \n
                1. <\/b> A static LAG can contain only one physical interface<\/span><\/li>\n
                2. <\/b> Static LAGs cannot carry VLAN traffic<\/span><\/li>\n
                3. <\/b> There is no LACP signaling to detect certain peer-side misconfigurations or link conditions<\/span><\/li>\n
                4. <\/b> Static LAGs require BGP<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. There is no LACP signaling to detect certain peer-side misconfigurations or link conditions<\/b><\/p>\n

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

                  A static LAG creates an aggregation without exchanging LACP protocol messages. Because there is no keepalive or negotiation process between the devices, certain mismatches can be more difficult to detect. HPE documentation warns that static mode has no LACP PDU communication, so a configuration problem on one side can cause difficult troubleshooting conditions. LACP adds protocol signaling that allows peers to negotiate the aggregation and monitor member behavior. Static LAGs can still be appropriate where LACP is unavailable, but both endpoints must be configured consistently.<\/span><\/p>\n

                  Question 109. What is the PRIMARY purpose of DHCP snooping on an AOS-CX access switch?<\/b><\/p>\n

                    \n
                  1. <\/b> To protect clients from rogue or unauthorized DHCP servers and build trusted DHCP bindings<\/span><\/li>\n
                  2. <\/b> To provide DNS resolution<\/span><\/li>\n
                  3. <\/b> To create VLAN trunks<\/span><\/li>\n
                  4. <\/b> To replace the DHCP server<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. To protect clients from rogue or unauthorized DHCP servers and build trusted DHCP bindings<\/b><\/p>\n

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

                    DHCP snooping protects the access network by distinguishing trusted DHCP infrastructure from ordinary untrusted client-facing ports. DHCP server messages received from unauthorized locations can be inspected and dropped, helping prevent a rogue device from providing false IP addressing, gateway, or DNS information. HPE also notes that DHCP snooping can build IP binding information from legitimate DHCP exchanges. Those bindings can support additional security mechanisms, such as IP source lockdown. DHCP snooping therefore protects the DHCP process; it does not itself replace the DHCP server that assigns addresses.<\/span><\/p>\n

                    Question 110. Which interface should normally be marked as trusted for DHCP snooping?<\/b><\/p>\n

                      \n
                    1. <\/b> Every desktop-facing access interface<\/span><\/li>\n
                    2. <\/b> Every unused port<\/span><\/li>\n
                    3. <\/b> An uplink or interface leading toward the legitimate DHCP server infrastructure<\/span><\/li>\n
                    4. <\/b> Only the switch console port<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 3. An uplink or interface leading toward the legitimate DHCP server infrastructure<\/b><\/p>\n

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

                      DHCP snooping trust should be assigned only to interfaces through which legitimate DHCP server messages are expected to arrive. In a typical campus, this means uplinks toward authorized DHCP servers, relays, or trusted network infrastructure. User-facing access ports remain untrusted so a malicious or accidental DHCP server connected by an endpoint cannot distribute addresses to clients. HPE’s DHCP snooping use case specifically shows trusted uplink ports and untrusted LAN-facing user interfaces. Incorrectly trusting access ports weakens one of DHCP snooping’s primary protections.<\/span><\/p>\n

                      Question 111. What is the purpose of configuring an authorized DHCP server address with DHCP snooping?<\/b><\/p>\n

                        \n
                      1. <\/b> To convert the switch into that DHCP server<\/span><\/li>\n
                      2. <\/b> To identify which DHCP server addresses are permitted to provide service<\/span><\/li>\n
                      3. <\/b> To configure the switch’s default gateway<\/span><\/li>\n
                      4. <\/b> To disable DHCP binding learning<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 2. To identify which DHCP server addresses are permitted to provide service<\/b><\/p>\n

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

                        An authorized-server configuration lets the switch identify legitimate DHCP servers by IP address. This adds another control beyond simply trusting an uplink interface. HPE’s documented DHCP snooping examples configure authorized DHCP server addresses and trusted uplinks so the switch can distinguish valid infrastructure from rogue DHCP services. Such protections are important because an attacker-controlled DHCP server could otherwise provide clients with malicious addressing parameters and redirect their traffic. DHCP snooping should be designed together with VLAN scope and interface trust so legitimate DHCP messages continue to operate normally.<\/span><\/p>\n

                        Question 112. Can DHCP relay and DHCP snooping operate on the same supported AOS-CX switch?<\/b><\/p>\n

                          \n
                        1. <\/b> No, they are always mutually exclusive<\/span><\/li>\n
                        2. <\/b> Only if no VLANs are configured<\/span><\/li>\n
                        3. <\/b> Only when the switch is acting as the DHCP server<\/span><\/li>\n
                        4. <\/b> Yes, DHCP snooping and DHCP relay can coexist on supported platforms<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 4. Yes, DHCP snooping and DHCP relay can coexist on supported platforms<\/b><\/p>\n

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

                          HPE documentation states that DHCP snooping and DHCP relay can coexist on the same supported switch. When both are enabled, DHCP snooping inspects received DHCP packets before they are handed to the relay function, and snooping can also observe DHCP messages transmitted by the relay to learn bindings. This allows a Layer 3 access switch to relay DHCP requests to remote servers while still receiving the security benefits of DHCP snooping. Platform-specific limitations should always be checked, but these two functions are not inherently mutually exclusive.<\/span><\/p>\n

                          Question 113. What is the PRIMARY purpose of IP source lockdown on AOS-CX?<\/b><\/p>\n

                            \n
                          1. <\/b> To prevent unknown BGP neighbors<\/span><\/li>\n
                          2. <\/b> To assign a VLAN dynamically<\/span><\/li>\n
                          3. <\/b> To allow client traffic only when the source MAC and IP information matches a valid binding<\/span><\/li>\n
                          4. <\/b> To encrypt all Layer 3 traffic<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3. To allow client traffic only when the source MAC and IP information matches a valid binding<\/b><\/p>\n

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

                            IP source lockdown provides stronger source validation for client traffic. HPE documentation states that when the feature is enabled, traffic from a client is permitted only when the client’s MAC and IP address correspond to information present in the binding database. DHCP snooping is one common source of those bindings. This helps prevent users from simply configuring an unauthorized or spoofed source IP address and sending traffic through the access network. Because the protection depends on accurate binding information, administrators must ensure DHCP snooping or the appropriate binding mechanism is operating correctly before enforcing lockdown.<\/span><\/p>\n

                            Question 114. Why is BPDU Guard commonly enabled on user-facing edge ports?<\/b><\/p>\n

                              \n
                            1. <\/b> To protect the spanning-tree topology from unexpected BPDUs received from endpoint-facing interfaces<\/span><\/li>\n
                            2. <\/b> To increase PoE power automatically<\/span><\/li>\n
                            3. <\/b> To configure LACP Active mode<\/span><\/li>\n
                            4. <\/b> To provide DHCP relay<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1. To protect the spanning-tree topology from unexpected BPDUs received from endpoint-facing interfaces<\/b><\/p>\n

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

                              An edge port connected to an ordinary endpoint should not normally receive spanning-tree BPDUs. If BPDUs appear on such a port, someone may have connected an unauthorized switch, created an accidental bridging loop, or introduced another unexpected Layer 2 device. BPDU Guard protects the network by treating that event as a violation and taking protective action according to the platform’s behavior. HPE’s current AOS-CX access-port configuration guidance includes BPDU Guard among recommended loop-prevention settings for campus edge ports. This helps keep end-user ports from unexpectedly participating in the spanning-tree topology.<\/span><\/p>\n

                              Question 115. What is the PRIMARY purpose of loop protection on an AOS-CX access interface?<\/b><\/p>\n

                                \n
                              1. <\/b> To assign IP addresses to endpoints<\/span><\/li>\n
                              2. <\/b> To select the LACP system ID<\/span><\/li>\n
                              3. <\/b> To change a port into a trunk automatically<\/span><\/li>\n
                              4. <\/b> To detect and respond to Layer 2 loop conditions on ports where loops should not occur<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 4. To detect and respond to Layer 2 loop conditions on ports where loops should not occur<\/b><\/p>\n

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

                                Loop protection is intended for switch interfaces where an unexpected loop could cause significant disruption, such as access-layer ports. Layer 2 loops can generate repeated frame circulation, MAC-table instability, and broadcast storms. HPE’s current Central-based AOS-CX access configuration examples include loop protection together with BPDU Guard for edge-port hardening. Loop protection is complementary to spanning tree: rather than replacing STP, it gives administrators an additional mechanism for detecting loop conditions on interfaces where receiving the device’s own loop-protection traffic indicates an abnormal topology.<\/span><\/p>\n

                                Question 116. What is the PRIMARY purpose of Power over Ethernet (PoE) on a campus access switch?<\/b><\/p>\n

                                  \n
                                1. <\/b> To provide routing between VLANs<\/span><\/li>\n
                                2. <\/b> To deliver electrical power and Ethernet connectivity over the same cabling to supported endpoints<\/span><\/li>\n
                                3. <\/b> To create a VSF stack<\/span><\/li>\n
                                4. <\/b> To encrypt switch management traffic<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. To deliver electrical power and Ethernet connectivity over the same cabling to supported endpoints<\/b><\/p>\n

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

                                  PoE allows a supported switch port to provide electrical power to connected powered devices while simultaneously carrying Ethernet data. Common campus PoE endpoints include access points, IP phones, cameras, and some IoT systems. This simplifies deployment because those devices may not require a separate local power adapter or nearby electrical outlet. HPE’s current Central interface profiles include PoE configuration for supported switch models, including enablement, power priority, and allocation method. PoE capacity should still be planned according to the switch’s available power budget and the requirements of attached devices.<\/span><\/p>\n

                                  Question 117. Why is PoE priority useful on an access switch?<\/b><\/p>\n

                                    \n
                                  1. <\/b> It determines which VLAN wins an STP election<\/span><\/li>\n
                                  2. <\/b> It changes a port’s MAC address<\/span><\/li>\n
                                  3. <\/b> It replaces endpoint authentication<\/span><\/li>\n
                                  4. <\/b> It helps determine which powered devices should retain power when the switch does not have enough PoE capacity for every request<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 4. It helps determine which powered devices should retain power when the switch does not have enough PoE capacity for every request<\/b><\/p>\n

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

                                    A switch has a finite PoE power budget. If connected powered devices collectively request more power than the switch can supply, PoE priority helps the system decide which ports or devices should receive power first. Administrators can give critical devices\u2014such as access points, emergency phones, or security systems\u2014a higher power priority than less critical endpoints. HPE Central exposes PoE priority and allocation controls in supported interface profiles. Proper prioritization helps maintain availability of important services during power-budget constraints instead of treating every connected powered device as equally critical.<\/span><\/p>\n

                                    Question 118. What is the PRIMARY purpose of LLDP on a campus access switch?<\/b><\/p>\n

                                      \n
                                    1. <\/b> To distribute dynamic IP routes<\/span><\/li>\n
                                    2. <\/b> To exchange identification and capability information with directly connected Layer 2 neighbors<\/span><\/li>\n
                                    3. <\/b> To provide DHCP addresses<\/span><\/li>\n
                                    4. <\/b> To establish VPN tunnels<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 2. To exchange identification and capability information with directly connected Layer 2 neighbors<\/b><\/p>\n

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

                                      Link Layer Discovery Protocol allows directly connected devices to advertise information about themselves to neighboring devices. This can include device identification, port details, system capabilities, and other supported attributes. LLDP is particularly useful in campus environments containing IP phones, access points, switches, and other infrastructure because it improves topology visibility and can support device-specific operational behavior. HPE’s current switch configuration guidance enables LLDP transmit and receive functions on typical access-port profiles. LLDP operates at Layer 2 and does not require the neighboring device to form an IP routing relationship.<\/span><\/p>\n

                                      Question 119. What is the PRIMARY purpose of the dedicated management interface on supported AOS-CX switches?<\/b><\/p>\n

                                        \n
                                      1. <\/b> To provide out-of-band management connectivity separate from normal production data interfaces<\/span><\/li>\n
                                      2. <\/b> To carry every user VLAN<\/span><\/li>\n
                                      3. <\/b> To operate as an LACP member only<\/span><\/li>\n
                                      4. <\/b> To power access points<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3. To provide out-of-band management connectivity separate from normal production data interfaces<\/b><\/p>\n

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

                                        Supported AOS-CX switches include a dedicated management interface that can be used for out-of-band management. This separates administrative connectivity from ordinary production switching and routing interfaces. HPE onboarding documentation shows the management interface configured with its own address, default gateway, and DNS information, and HPE Central profiles can manage its settings independently. Out-of-band management is valuable because administrators may still be able to reach the switch even when the production VLAN or routing configuration has a problem. It also supports clearer separation between management traffic and user traffic.<\/span><\/p>\n

                                        Question 120. An enterprise is deploying AOS-CX access switches for PCs, APs, phones, and cameras. It wants resilient uplinks, protection from rogue DHCP servers, source-address enforcement, protection against accidental edge loops, and power for APs and phones. Which design BEST meets the requirements?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Use LACP-based uplink LAGs, DHCP snooping with trusted uplinks, IP source lockdown, BPDU Guard\/loop protection on edge ports, and PoE for supported endpoints<\/span><\/li>\n
                                        2. <\/b> Configure every port as an unrestricted trunk and disable DHCP inspection<\/span><\/li>\n
                                        3. <\/b> Use static routes only and connect powered devices to ordinary non-PoE ports<\/span><\/li>\n
                                        4. <\/b> Trust every access port for DHCP and disable Layer 2 protections<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 1. Use LACP-based uplink LAGs, DHCP snooping with trusted uplinks, IP source lockdown, BPDU Guard\/loop protection on edge ports, and PoE for supported endpoints<\/b><\/p>\n

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

                                          Each requirement maps to a specific campus-access capability. LACP-based LAGs provide resilient uplinks and protocol-based link aggregation. DHCP snooping identifies trusted DHCP infrastructure and blocks unauthorized DHCP server behavior on user-facing interfaces. IP source lockdown enforces valid client IP\/MAC bindings. BPDU Guard and loop protection harden endpoint-facing ports against accidental or unauthorized Layer 2 loops. PoE allows access points, phones, cameras, and other powered devices to receive both data and electrical power from the switch. Together, these features provide a practical and secure HPE Aruba Networking campus access design.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full HP HPE6-A85 Exam Dumps and Practice Test Dumps. Question 101. On an AOS-CX switch, what is the PRIMARY purpose of configuring an interface as an access port? To carry every VLAN configured on the switch To associate ordinary untagged endpoint traffic with a single access VLAN To establish an LACP bundle automatically To […]<\/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\/21470"}],"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=21470"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21470\/revisions"}],"predecessor-version":[{"id":21471,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21470\/revisions\/21471"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21470"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21470"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21470"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}