{"id":21354,"date":"2026-09-24T12:14:54","date_gmt":"2026-09-24T12:14:54","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21354"},"modified":"2026-09-24T12:14:54","modified_gmt":"2026-09-24T12:14:54","slug":"cyberark-cpc-sen-practice-test-questions-and-exam-dumps-part9-q161-180","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cyberark-cpc-sen-practice-test-questions-and-exam-dumps-part9-q161-180\/","title":{"rendered":"CyberArk CPC-SEN Practice Test Questions and Exam Dumps Part9 Q161-180"},"content":{"rendered":"

View Full <\/b>CyberArk CPC-SEN Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/p>\n


\n<\/b>Question 161. What is the PRIMARY purpose of the CyberArk Access Control Policies API in a modern PAM environment?<\/b><\/p>\n

    \n
  1. <\/b> To generate operating-system patches<\/span><\/li>\n
  2. <\/b> To back up PSM recordings<\/span><\/li>\n
  3. <\/b> To manage policies that enforce privileged access rules, including Zero Standing Privileges across cloud and infrastructure resources<\/span><\/li>\n
  4. <\/b> To replace CyberArk Identity authentication<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. To manage policies that enforce privileged access rules, including Zero Standing Privileges across cloud and infrastructure resources<\/b><\/p>\n

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

    The Access Control Policies API allows organizations to manage policy-driven privileged access programmatically. CyberArk describes this API as supporting policies that enforce Zero Standing Privileges across cloud and infrastructure environments. Policies define who may obtain access, which resources are in scope, and under what conditions privilege can be granted. Using an API also makes it possible to integrate privileged-access policy administration with automation and infrastructure workflows. This does not replace user authentication or session monitoring; rather, it automates the authorization layer that determines how privileged access is governed.<\/span><\/p>\n

    Question 162. What is the purpose of the CyberArk Access Requests API?<\/b><\/p>\n

      \n
    1. <\/b> To view and manage requests for privileged access<\/span><\/li>\n
    2. <\/b> To rotate CPM service-account passwords<\/span><\/li>\n
    3. <\/b> To configure the Digital Vault firewall<\/span><\/li>\n
    4. <\/b> To generate PSM connection components<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. To view and manage requests for privileged access<\/b><\/p>\n

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

      The Access Requests API provides programmatic access to privileged-access request workflows. It can be used to view and manage requests that users submit when they need temporary or governed elevated access. This is especially useful in modern PAM environments where access is time-bound, policy-driven, or based on Zero Standing Privileges rather than permanently assigned administrator roles. Organizations can integrate approval and request workflows with service-management or automation systems while preserving centralized governance. The API handles the request lifecycle; it does not replace the underlying authorization policies, authentication mechanisms, or session controls.<\/span><\/p>\n

      Question 163. Which CyberArk API is designed to automate tasks related to cloud identities and their entitlements across cloud service providers?<\/b><\/p>\n

        \n
      1. <\/b> Secrets Hub API<\/span><\/li>\n
      2. <\/b> Identity API<\/span><\/li>\n
      3. <\/b> Workspace Delegation API<\/span><\/li>\n
      4. <\/b> Cloud Discovery Service API<\/span><\/li>\n<\/ol>\n

        Correct Answer: 4. Cloud Discovery Service API<\/b><\/p>\n

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

        CyberArk identifies the Cloud Discovery Service API as the interface for automating tasks related to cloud identities and their entitlements across supported cloud providers. Discovery is an important part of modern PAM because privilege is no longer limited to traditional administrator accounts. Cloud roles, workload identities, developers, machine identities, and automation can all accumulate powerful permissions. Automated discovery helps organizations locate this privilege, understand exposure, and apply appropriate controls. The API supports automation of discovery-related workflows rather than session recording or traditional CPM password management.<\/span><\/p>\n

        Question 164. What is the PRIMARY purpose of the CyberArk Risk Management API?<\/b><\/p>\n

          \n
        1. <\/b> To create privileged passwords<\/span><\/li>\n
        2. <\/b> To retrieve risk information associated with discovered entities<\/span><\/li>\n
        3. <\/b> To provide VPN connectivity<\/span><\/li>\n
        4. <\/b> To modify PSM recordings<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2. To retrieve risk information associated with discovered entities<\/b><\/p>\n

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

          The Risk Management API provides information about risk associated with identities or entities discovered by CyberArk’s modern privilege and cloud-security services. Risk context helps organizations prioritize which identities, entitlements, or resources require stronger controls first. Rather than treating every discovered account or permission as equally urgent, administrators can focus on privilege that presents greater exposure. This supports a risk-based PAM approach in which discovery, analysis, least privilege, and remediation work together. The Risk Management API supplies risk information; it does not itself rotate credentials or broker privileged sessions.<\/span><\/p>\n

          Question 165. What is the PRIMARY purpose of the CyberArk Workspace Delegation API?<\/b><\/p>\n

            \n
          1. <\/b> To create, update, search, delete, and manage user and role delegations to cloud workspaces<\/span><\/li>\n
          2. <\/b> To configure password complexity on Windows servers<\/span><\/li>\n
          3. <\/b> To replace SAML authentication<\/span><\/li>\n
          4. <\/b> To store PSM video files<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. To create, update, search, delete, and manage user and role delegations to cloud workspaces<\/b><\/p>\n

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

            The Workspace Delegation API supports programmatic management of user and role delegation to cloud workspaces. This is useful when organizations need controlled, scalable administration of who may act within particular cloud environments or delegated workspaces. Delegation should follow least-privilege principles so users receive only the rights needed for their responsibilities. Automating delegation through an API can reduce manual administrative effort and improve consistency, especially across large cloud estates. This capability is distinct from credential vaulting or session recording because it focuses on delegated cloud access and authorization.<\/span><\/p>\n

            Question 166. Which CyberArk API family is MOST directly associated with securely viewing and accessing infrastructure assets through modern privileged access?<\/b><\/p>\n

              \n
            1. <\/b> Secrets Hub API<\/span><\/li>\n
            2. <\/b> Certificate Manager API<\/span><\/li>\n
            3. <\/b> Secure Infrastructure Access API<\/span><\/li>\n
            4. <\/b> Email Security API<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3. Secure Infrastructure Access API<\/b><\/p>\n

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

              CyberArk’s Secure Infrastructure Access API is designed to view and manage infrastructure resources used in secure privileged-access workflows. Secure Infrastructure Access supports modern approaches such as controlled access to infrastructure, monitored sessions, and Zero Standing Privileges. The API enables integrations and automation around those protected resources instead of requiring all actions to be performed manually through a graphical interface. SIA complements more traditional vaulted credential workflows and helps organizations extend PAM into cloud and hybrid infrastructure where just-in-time or ZSP access may be preferable.<\/span><\/p>\n

              Question 167. What is the PRIMARY purpose of CyberArk API tokens?<\/b><\/p>\n

                \n
              1. <\/b> To replace target-system administrator passwords permanently<\/span><\/li>\n
              2. <\/b> To authenticate authorized programmatic access to CyberArk APIs<\/span><\/li>\n
              3. <\/b> To provide session recordings<\/span><\/li>\n
              4. <\/b> To act as reconciliation accounts<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. To authenticate authorized programmatic access to CyberArk APIs<\/b><\/p>\n

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

                API tokens are used to authenticate programmatic requests to supported CyberArk APIs. They enable automation tools, scripts, and integrations to interact securely with CyberArk services without relying on an interactive browser login for every request. Tokens should be protected as sensitive credentials because possession of a valid token can permit access according to the token’s authorization scope. Administrators should follow least privilege, limit token exposure, rotate or revoke tokens when appropriate, and avoid embedding them insecurely in source code or scripts. CyberArk’s API portal explicitly provides guidance for creating API tokens.<\/span><\/p>\n

                Question 168. Why does CyberArk apply API rate limiting?<\/b><\/p>\n

                  \n
                1. <\/b> To ensure every API call changes a password<\/span><\/li>\n
                2. <\/b> To prevent users from authenticating through SSO<\/span><\/li>\n
                3. <\/b> To disable automation<\/span><\/li>\n
                4. <\/b> To control request volume and help protect service stability and availability<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4. To control request volume and help protect service stability and availability<\/b><\/p>\n

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

                  API rate limiting restricts how many requests a client can send within a defined period. This protects shared services from excessive traffic, accidental request loops, or abusive automation that could affect performance and availability. Administrators building CyberArk integrations should design scripts to handle limits gracefully, including appropriate retry logic and backoff behavior. Rate limiting does not mean automation is discouraged; it means automation should operate predictably and responsibly. CyberArk’s API documentation explicitly calls out rate limiting as part of the platform’s API usage model.<\/span><\/p>\n

                  Question 169. What is the security advantage of using CyberArk APIs to automate access governance instead of manually granting permanent administrator roles?<\/b><\/p>\n

                    \n
                  1. <\/b> APIs eliminate the need for authentication<\/span><\/li>\n
                  2. <\/b> APIs make every user a Safe owner<\/span><\/li>\n
                  3. <\/b> Automation can apply consistent, time-bound, policy-driven access instead of persistent privilege<\/span><\/li>\n
                  4. <\/b> Automation prevents all cloud outages<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 2. Automation can apply consistent, time-bound, policy-driven access instead of persistent privilege<\/b><\/p>\n

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

                    Modern PAM is increasingly focused on reducing permanent privileged access. By integrating access requests, policy enforcement, delegation, and ZSP through APIs, organizations can grant privilege dynamically based on documented rules rather than leaving powerful roles assigned indefinitely. Automation also improves consistency because the same access logic can be applied across many users and resources. Human approval may still be required for certain high-risk requests, but the process can remain governed and auditable. CyberArk’s modern platform emphasizes ZSP, just-in-time privilege, and automated identity-security controls.<\/span><\/p>\n

                    Question 170. Which CyberArk capability is MOST appropriate for managing secrets while allowing them to be consumed natively in a cloud platform?<\/b><\/p>\n

                      \n
                    1. <\/b> PSM<\/span><\/li>\n
                    2. <\/b> CPM Verify<\/span><\/li>\n
                    3. <\/b> Dual Control<\/span><\/li>\n
                    4. <\/b> Secrets Hub API<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4. Secrets Hub API<\/b><\/p>\n

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

                      CyberArk describes the secrets hub API as a way to manage secrets in the PAM solution while enabling those secrets to be consumed natively within cloud platforms. This supports modern workloads that need application or machine credentials without forcing every workload to use an interactive human PAM process. Secrets remain centrally governed while being synchronized or made available through supported cloud-native mechanisms. Secrets Hub therefore addresses machine identity and application-secret use cases rather than interactive PSM sessions or traditional human privileged-password retrieval.<\/span><\/p>\n

                      Question 171. Why are machine identities a major concern in modern PAM?<\/b><\/p>\n

                        \n
                      1. <\/b> Applications, automation, AI agents, and services can hold powerful permissions and secrets that attackers may exploit<\/span><\/li>\n
                      2. <\/b> Machine identities can never authenticate<\/span><\/li>\n
                      3. <\/b> Machine identities never require credentials<\/span><\/li>\n
                      4. <\/b> Only human accounts can receive privileges<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. Applications, automation, AI agents, and services can hold powerful permissions and secrets that attackers may exploit<\/b><\/p>\n

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

                        Modern environments contain large numbers of non-human identities, including services, applications, automation pipelines, workload identities, and AI agents. These identities often possess powerful credentials or entitlements but may receive less oversight than human administrators. CyberArk’s current platform strategy explicitly extends identity security to both human and machine identities. Discovery, secrets management, risk analysis, and modern access controls are therefore important because compromise of a machine identity can provide attackers with direct access to sensitive infrastructure or cloud services.<\/span><\/p>\n

                        Question 172. What is the PRIMARY benefit of CyberArk’s SaaS-based Discovery service compared with relying only on manual account inventories?<\/b><\/p>\n

                          \n
                        1. <\/b> It eliminates the need for privileged-access controls<\/span><\/li>\n
                        2. <\/b> It disables account creation<\/span><\/li>\n
                        3. <\/b> It provides continuous visibility across multiple environments and identity types<\/span><\/li>\n
                        4. <\/b> It automatically deletes every risky account<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. It provides continuous visibility across multiple environments and identity types<\/b><\/p>\n

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

                          Manual privileged-account inventories become outdated quickly in dynamic environments. CyberArk’s SaaS-based Discovery service is designed to continuously identify privileged accounts and identities across Windows, UNIX-like systems, endpoints, cloud services, and application secrets. CyberArk also highlights coverage for both human and machine identities and supports automated scans, remediation, and risk insights. Continuous discovery reduces blind spots created when new accounts or entitlements appear after the last manual review. It provides visibility and context, while administrators still decide which security controls and remediation actions should follow.<\/span><\/p>\n

                          Question 173. Which CyberArk shared-service capability can automatically identify anomalous privileged behavior and provide recommended responses?<\/b><\/p>\n

                            \n
                          1. <\/b> Safe Backup<\/span><\/li>\n
                          2. <\/b> Password Reconcile<\/span><\/li>\n
                          3. <\/b> Connector Upgrade<\/span><\/li>\n
                          4. <\/b> Detection and Response<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 4. Detection and Response<\/b><\/p>\n

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

                            CyberArk’s Detection and Response capability analyzes privileged and workforce activity for signs of anomalous or risky behavior. CyberArk describes the service as producing real-time alerts and recommended responses to help security teams identify and analyze high-risk events more quickly. This is important because a session can be properly authenticated yet still become malicious if the identity is compromised or behaves unexpectedly. Detection and Response therefore complements preventive controls such as MFA, least privilege, credential rotation, and Zero Standing Privileges.<\/span><\/p>\n

                            Question 174. What is a PRIMARY advantage of Idira\/CyberArk Identity Administration shared services for PAM users?<\/b><\/p>\n

                              \n
                            1. <\/b> It replaces CPM credential management<\/span><\/li>\n
                            2. <\/b> It provides a consistent authentication, authorization, user, and role-management layer across services<\/span><\/li>\n
                            3. <\/b> It disables Safe permissions<\/span><\/li>\n
                            4. <\/b> It removes the need for MFA<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2. It provides a consistent authentication, authorization, user, and role-management layer across services<\/b><\/p>\n

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

                              Identity Administration provides a common identity foundation across CyberArk’s SaaS services. CyberArk highlights consistent user identity and role management, authentication and authorization, support for cloud directories, and self-service SAML, LDAP, RADIUS, SSO, and MFA configuration. This reduces fragmentation across products and helps users authenticate through a common identity layer while each service still applies its own privileged authorization and security policies. Identity Administration complements PAM rather than replacing credential rotation, Safe permissions, or session controls.<\/span><\/p>\n

                              Question 175. What is the PRIMARY operational advantage of CyberArk’s centralized connector upgrade capabilities?<\/b><\/p>\n

                                \n
                              1. <\/b> They allow supported CPM and PSM upgrades to be initiated remotely without manually servicing each connector server<\/span><\/li>\n
                              2. <\/b> They eliminate the need for connector servers<\/span><\/li>\n
                              3. <\/b> They disable high availability<\/span><\/li>\n
                              4. <\/b> They permanently prevent component failures<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 3. They allow supported CPM and PSM upgrades to be initiated remotely without manually servicing each connector server<\/b><\/p>\n

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

                                CyberArk’s modern Privilege Cloud management reduces administrative overhead by supporting remote upgrades for CPM and PSM components through centralized connector management. This is especially valuable in large environments with multiple connector servers, where manual logon and upgrade of each component would consume significant time and increase inconsistency. CyberArk also supports upgrades through configured proxies in restricted network environments. Centralized upgrades improve operational efficiency, but organizations should still plan maintenance, redundancy, rollback, and compatibility appropriately.<\/span><\/p>\n

                                Question 176. Which CyberArk component in the hosted Privilege Cloud infrastructure provides the frontend console used by customers?<\/b><\/p>\n

                                  \n
                                1. <\/b> Web server<\/span><\/li>\n
                                2. <\/b> Reconciliation account<\/span><\/li>\n
                                3. <\/b> PSMConnect user<\/span><\/li>\n
                                4. <\/b> Safe owner<\/span><\/li>\n<\/ol>\n

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

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

                                  CyberArk’s Privilege Cloud SOC report identifies web servers as the frontend infrastructure providing the console into Privilege Cloud. The hosted service also includes database, storage, monitoring, firewall, and other backend infrastructure. Customer-side connector servers establish encrypted tunnels between customer systems and the Privilege Cloud backend, but they do not provide the SaaS user interface itself. Understanding this separation helps distinguish the hosted control plane from customer-operated connector infrastructure.<\/span><\/p>\n

                                  Question 177. Which hosted service is identified as the Privilege Cloud application’s relational database in CyberArk’s architecture documentation?<\/b><\/p>\n

                                    \n
                                  1. <\/b> Microsoft Access<\/span><\/li>\n
                                  2. <\/b> Amazon Aurora-based relational database service<\/span><\/li>\n
                                  3. <\/b> Local SQLite on each connector<\/span><\/li>\n
                                  4. <\/b> Active Directory<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 2. Amazon Aurora-based relational database service<\/b><\/p>\n

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

                                    CyberArk’s published Privilege Cloud architecture identifies an Aurora relational database service as the database layer containing Privilege Cloud application data. This is part of CyberArk’s SaaS backend and is distinct from the Linux-based Privilege Cloud Connector Servers operated to connect customer systems securely to the cloud service. Customers do not manage this database as though it were a local PAM component. The distinction reinforces the SaaS model: CyberArk operates the backend service infrastructure while customers manage their own connectors, targets, accounts, policies, and access configuration.<\/span><\/p>\n

                                    Question 178. What is the PRIMARY purpose of cloud monitoring services in the CyberArk Privilege Cloud backend?<\/b><\/p>\n

                                      \n
                                    1. <\/b> To support centralized logging and monitoring of the hosted service<\/span><\/li>\n
                                    2. <\/b> To act as CPM for customer passwords<\/span><\/li>\n
                                    3. <\/b> To create target-system accounts<\/span><\/li>\n
                                    4. <\/b> To provide LDAP authentication to customer domains<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 1. To support centralized logging and monitoring of the hosted service<\/b><\/p>\n

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

                                      CyberArk’s architecture documentation identifies cloud monitoring as part of the hosted Privilege Cloud infrastructure. The monitoring service supports operational logging and visibility for the SaaS backend, helping CyberArk operate and maintain the service. This is distinct from customer-facing privileged-session monitoring and auditing, which focus on administrator activity on target systems. Backend service monitoring helps CyberArk identify operational or infrastructure issues within the SaaS environment, while PAM auditing and session monitoring address how privileged users interact with protected resources.<\/span><\/p>\n

                                      Question 179. Why does CyberArk use host-based and hardware firewalls within Privilege Cloud infrastructure?<\/b><\/p>\n

                                        \n
                                      1. <\/b> To rotate managed passwords<\/span><\/li>\n
                                      2. <\/b> To approve privileged access requests<\/span><\/li>\n
                                      3. <\/b> To generate session recordings<\/span><\/li>\n
                                      4. <\/b> To harden access to the service and reduce lateral movement between infrastructure components<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 4. To harden access to the service and reduce lateral movement between infrastructure components<\/b><\/p>\n

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

                                        CyberArk’s published architecture identifies host-based and hardware firewalls as infrastructure controls used to harden access to Privilege Cloud and prevent lateral movement from one server to another. Network segmentation and firewalling reduce the impact of a potential compromise by limiting which systems can communicate directly. These controls protect the SaaS infrastructure itself and complement the PAM controls CyberArk provides to customers. Firewalls do not replace identity verification, Safe permissions, or session monitoring; they form part of the underlying defense-in-depth architecture.<\/span><\/p>\n

                                        Question 180. An enterprise wants to automate temporary cloud privilege, discover risky human and machine identities, centralize authentication, and analyze anomalous privileged behavior. Which CyberArk design BEST meets these requirements?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Use permanent cloud administrator roles and manual spreadsheets<\/span><\/li>\n
                                        2. <\/b> Use only traditional password vaulting with no discovery or identity integration<\/span><\/li>\n
                                        3. <\/b> Combine Access Control Policies and Access Requests for governed temporary access, SaaS-based Discovery and Risk Management for visibility, Identity Administration for authentication, and Detection and Response for anomalous behavior<\/span><\/li>\n
                                        4. <\/b> Disable APIs and automate nothing<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. Combine Access Control Policies and Access Requests for governed temporary access, SaaS-based Discovery and Risk Management for visibility, Identity Administration for authentication, and Detection and Response for anomalous behavior<\/b><\/p>\n

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

                                          The requirements span several layers of modern PAM. Access Control Policies and Access Requests support governed and temporary privileged access, including ZSP models. SaaS-based Discovery identifies privileged human and machine identities, while risk information helps prioritize exposure. Identity Administration provides a common authentication and authorization foundation with SSO and MFA capabilities. Detection and Response identifies anomalous use and can recommend actions when privileged behavior becomes risky. Combining these services creates a modern identity-security architecture that addresses visibility, prevention, access governance, authentication, and response rather than relying on permanent privileges or vaulting alone.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full CyberArk CPC-SEN Exam Dumps and Practice Test Dumps. Question 161. What is the PRIMARY purpose of the CyberArk Access Control Policies API in a modern PAM environment? To generate operating-system patches To back up PSM recordings To manage policies that enforce privileged access rules, including Zero Standing Privileges across cloud and infrastructure resources […]<\/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\/21354"}],"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=21354"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21354\/revisions"}],"predecessor-version":[{"id":21355,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21354\/revisions\/21355"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21354"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21354"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21354"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}