{"id":21368,"date":"2026-09-24T12:16:44","date_gmt":"2026-09-24T12:16:44","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21368"},"modified":"2026-09-24T12:16:44","modified_gmt":"2026-09-24T12:16:44","slug":"cyberark-cpc-sen-practice-test-questions-and-exam-dumps-part16-q301-320","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cyberark-cpc-sen-practice-test-questions-and-exam-dumps-part16-q301-320\/","title":{"rendered":"CyberArk CPC-SEN Practice Test Questions and Exam Dumps Part16 Q301-320"},"content":{"rendered":"

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


\n<\/b>Question 301. What is the PRIMARY purpose of an Endpoint Privilege Manager policy?<\/b><\/p>\n

    \n
  1. <\/b> To configure Privilege Cloud Safe ownership<\/span><\/li>\n
  2. <\/b> To define how applications and privileged actions should be handled on managed endpoints<\/span><\/li>\n
  3. <\/b> To rotate passwords stored in the Digital Vault<\/span><\/li>\n
  4. <\/b> To configure PSM connection components<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. To define how applications and privileged actions should be handled on managed endpoints<\/b><\/p>\n

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

    CyberArk Endpoint Privilege Manager policies determine how endpoint activity should be treated. A policy can control whether an application is allowed, blocked, monitored, or elevated and can define which users, computers, or application conditions are in scope. This allows administrators to remove broad local administrator rights while still granting the specific privileges users need. Policy design is a central EPM administration skill because poor scoping can either create excessive privilege or disrupt legitimate applications. CyberArk’s current EPM Administration curriculum specifically covers configuration, policy creation, monitoring, agent deployment, and troubleshooting.<\/span><\/p>\n

    Question 302. Why should EPM policies be scoped to specific users, groups, computers, or application conditions whenever possible?<\/b><\/p>\n

      \n
    1. <\/b> To increase permanent local administrator membership<\/span><\/li>\n
    2. <\/b> To make all applications run elevated<\/span><\/li>\n
    3. <\/b> To disable monitoring<\/span><\/li>\n
    4. <\/b> To ensure privilege is granted only where the business requirement actually exists<\/span><\/li>\n<\/ol>\n

      Correct Answer: 4. To ensure privilege is granted only where the business requirement actually exists<\/b><\/p>\n

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

      Narrow policy scope supports least privilege. If an application needs elevation only for a development team, applying the same elevation to every endpoint unnecessarily expands risk. EPM administrators should therefore target policies according to relevant users, devices, applications, or other supported conditions. This reduces the blast radius of compromised identities and prevents unrelated users from receiving unnecessary administrative capabilities. Well-scoped policies are also easier to troubleshoot because administrators can determine exactly why a particular endpoint or user matched the policy instead of dealing with broad rules that affect the entire environment.<\/span><\/p>\n

      Question 303. What is a good first step before enforcing a new restrictive application-control policy across an entire organization?<\/b><\/p>\n

        \n
      1. <\/b> Observe application activity in a limited or controlled population and validate legitimate software requirements<\/span><\/li>\n
      2. <\/b> Immediately block every unknown application globally<\/span><\/li>\n
      3. <\/b> Grant all users temporary administrator rights<\/span><\/li>\n
      4. <\/b> Disable EPM event collection<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. Observe application activity in a limited or controlled population and validate legitimate software requirements<\/b><\/p>\n

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

        Restrictive endpoint policies can cause business disruption if administrators do not understand which applications users actually need. A phased approach allows the security team to observe application behavior, identify legitimate software, define appropriate trust rules, and correct false positives before broad enforcement. CyberArk’s EPM Administration course includes configuration, policy, deployment, monitoring, and troubleshooting because successful least-privilege programs require ongoing tuning rather than simply enabling a blanket blocking policy. A controlled pilot reduces risk and gives support teams time to prepare for expected user questions.<\/span><\/p>\n

        Question 304. What does an EPM elevation policy allow a standard user to do?<\/b><\/p>\n

          \n
        1. <\/b> Become a permanent local administrator<\/span><\/li>\n
        2. <\/b> Disable CyberArk monitoring<\/span><\/li>\n
        3. <\/b> Run an approved application or task with elevated privileges without receiving unrestricted administrator rights<\/span><\/li>\n
        4. <\/b> Retrieve passwords from Privilege Cloud<\/span><\/li>\n<\/ol>\n

          Correct Answer: 3. Run an approved application or task with elevated privileges without receiving unrestricted administrator rights<\/b><\/p>\n

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

          Elevation policies are a key method for balancing security and productivity. Instead of adding users permanently to the local Administrators group, EPM can elevate a specific approved application or administrative operation. The user remains a standard user for unrelated activity, reducing the privileges available to malware or an attacker who compromises the session. This implements least privilege more effectively than broad administrative membership. The goal is not to eliminate every elevated operation, but to ensure elevation occurs only for approved business requirements under centrally defined policy.<\/span><\/p>\n

          Question 305. What is the security advantage of using a trusted-source policy for approved software?<\/b><\/p>\n

            \n
          1. <\/b> It automatically makes every downloaded application safe<\/span><\/li>\n
          2. <\/b> It disables application-control decisions<\/span><\/li>\n
          3. <\/b> It gives all users administrative rights<\/span><\/li>\n
          4. <\/b> It allows EPM to treat applications from approved origins differently from untrusted software<\/span><\/li>\n<\/ol>\n

            Correct Answer: 4. It allows EPM to treat applications from approved origins differently from untrusted software<\/b><\/p>\n

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

            Trusted-source logic helps administrators distinguish software obtained through approved corporate channels from applications arriving through unknown or risky sources. For example, an organization may trust software distributed through its sanctioned software-management system while applying stricter controls to executables downloaded from uncontrolled websites. Trust should still be carefully defined because an overly broad trusted source can weaken application control. EPM policy design should combine source, application identity, user scope, and other available conditions to make elevation or execution decisions that are both secure and practical.<\/span><\/p>\n

            Question 306. Why should an administrator avoid defining overly broad elevation rules such as elevating every executable in a writable user folder?<\/b><\/p>\n

              \n
            1. <\/b> A malicious executable placed in that location could inherit the same elevation<\/span><\/li>\n
            2. <\/b> EPM cannot monitor writable folders<\/span><\/li>\n
            3. <\/b> Broad elevation improves security too much<\/span><\/li>\n
            4. <\/b> User folders cannot contain executable files<\/span><\/li>\n<\/ol>\n

              Correct Answer: 1. A malicious executable placed in that location could inherit the same elevation<\/b><\/p>\n

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

              Elevation rules should identify trusted applications as specifically as practical. If a rule simply elevates anything launched from a user-writable folder, an attacker or malware may be able to place a malicious executable there and obtain elevated privileges automatically. This undermines least privilege and turns the policy into an escalation path. Administrators should prefer stronger application-identification criteria and carefully controlled sources rather than relying only on locations users can modify. Policy review should always consider whether an attacker could manipulate the matching conditions.<\/span><\/p>\n

              Question 307. What is the PRIMARY function of the EPM agent installed on an endpoint?<\/b><\/p>\n

                \n
              1. <\/b> To store all Privilege Cloud passwords locally<\/span><\/li>\n
              2. <\/b> To replace the operating system<\/span><\/li>\n
              3. <\/b> To enforce EPM policies and report relevant endpoint activity<\/span><\/li>\n
              4. <\/b> To act as a PSM server<\/span><\/li>\n<\/ol>\n

                Correct Answer: 3. To enforce EPM policies and report relevant endpoint activity<\/b><\/p>\n

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

                The EPM agent is the enforcement component on managed endpoints. It evaluates endpoint activity against policies received from the EPM service and applies decisions such as elevation, blocking, or other configured actions. It also provides information that administrators can use for monitoring and troubleshooting. Agent deployment is therefore a dedicated area of EPM administration. If the agent is not installed, unhealthy, or unable to communicate properly, centrally defined policies may not be enforced as expected on that endpoint.<\/span><\/p>\n

                Question 308. A newly deployed endpoint is not receiving the expected EPM policy. What should the administrator check FIRST?<\/b><\/p>\n

                  \n
                1. <\/b> Rebuild every policy<\/span><\/li>\n
                2. <\/b> Verify that the EPM agent is installed, communicating, and associated with the expected policy scope<\/span><\/li>\n
                3. <\/b> Disable application control globally<\/span><\/li>\n
                4. <\/b> Give the user local administrator rights<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 2. Verify that the EPM agent is installed, communicating, and associated with the expected policy scope<\/b><\/p>\n

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

                  Before modifying a policy that works elsewhere, administrators should confirm that the affected endpoint is actually participating correctly in EPM management. The agent must be installed and healthy, the endpoint must be communicating with the service, and the user or computer must fall within the intended policy scope. A missing policy on one endpoint is often caused by deployment, communication, or targeting differences rather than a defective global rule. CyberArk EPM Administration training explicitly includes agent deployment, configuration, monitoring, and troubleshooting, reflecting this layered diagnostic approach.<\/span><\/p>\n

                  Question 309. What is the PRIMARY value of EPM event monitoring?<\/b><\/p>\n

                    \n
                  1. <\/b> It gives administrators visibility into endpoint privilege and application activity that can guide investigation and policy tuning<\/span><\/li>\n
                  2. <\/b> It replaces application-control policies<\/span><\/li>\n
                  3. <\/b> It automatically makes all events benign<\/span><\/li>\n
                  4. <\/b> It prevents users from logging on<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. It gives administrators visibility into endpoint privilege and application activity that can guide investigation and policy tuning<\/b><\/p>\n

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

                    Event monitoring provides evidence about what applications users run, which actions require elevation, which activities are blocked, and where policies may need refinement. This information helps security teams identify risky behavior and also reduces false positives by showing which legitimate workflows are being affected. Monitoring should be used before and after major policy changes so administrators can understand their impact. CyberArk’s EPM Administration curriculum includes monitoring as a core operational discipline rather than treating policy creation as a one-time configuration exercise.<\/span><\/p>\n

                    Question 310. A trusted business application suddenly generates an elevation denial for one department only. What should an administrator investigate FIRST?<\/b><\/p>\n

                      \n
                    1. <\/b> CPM reconciliation settings<\/span><\/li>\n
                    2. <\/b> Privilege Cloud Safe permissions<\/span><\/li>\n
                    3. <\/b> PSM recording retention<\/span><\/li>\n
                    4. <\/b> The EPM policy scope and conditions applying to that department<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4. The EPM policy scope and conditions applying to that department<\/b><\/p>\n

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

                      Because the issue affects only one department, the difference is likely related to policy targeting, user-group membership, endpoint grouping, or application conditions rather than a universal application problem. Administrators should compare which EPM policies apply to affected and unaffected users and confirm that the application still matches the expected policy criteria. This approach narrows the problem logically and avoids weakening controls for the entire organization. EPM troubleshooting should always consider scope, precedence, application identification, and agent state before broad policy changes.<\/span><\/p>\n

                      Question 311. What is the PRIMARY reason to use Just-In-Time elevation instead of permanent local administrator membership?<\/b><\/p>\n

                        \n
                      1. <\/b> To give administrators more permanent access<\/span><\/li>\n
                      2. <\/b> To provide elevated privilege only for the period in which it is needed<\/span><\/li>\n
                      3. <\/b> To disable endpoint auditing<\/span><\/li>\n
                      4. <\/b> To make every application trusted<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 2. To provide elevated privilege only for the period in which it is needed<\/b><\/p>\n

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

                        Just-In-Time elevation reduces standing privilege by limiting administrative rights to a defined period associated with a legitimate task. If the endpoint or user identity is compromised outside that window, the attacker does not automatically inherit permanent administrator privileges. JIT also improves governance because organizations can associate temporary elevation with specific maintenance or support activities. The access should expire automatically instead of depending on someone remembering to remove the user from an administrator group later. This mirrors broader Zero Standing Privilege principles used across modern CyberArk identity security.<\/span><\/p>\n

                        Question 312. What should an administrator do when a legitimate application is repeatedly blocked because EPM cannot reliably identify it using the current rule?<\/b><\/p>\n

                          \n
                        1. <\/b> Give the entire user population permanent administrator rights<\/span><\/li>\n
                        2. <\/b> Disable EPM on affected endpoints<\/span><\/li>\n
                        3. <\/b> Refine the application-identification criteria so the legitimate application is matched accurately without broadly trusting unrelated software<\/span><\/li>\n
                        4. <\/b> Allow every executable from the internet<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. Refine the application-identification criteria so the legitimate application is matched accurately without broadly trusting unrelated software<\/b><\/p>\n

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

                          A policy exception should solve the legitimate business need without opening an unnecessary security gap. If application identification is unreliable, administrators should refine the criteria using the strongest supported identifying characteristics rather than widening the rule to include unrelated executables. Broad exceptions can become privilege-escalation paths for attackers. EPM policy tuning is an iterative process: monitoring reveals failures, administrators adjust the rule, and the updated configuration should then be tested on a limited scope before organization-wide deployment.<\/span><\/p>\n

                          Question 313. What is a PRIMARY reason to separate EPM policies for developers, help-desk staff, and ordinary office users?<\/b><\/p>\n

                            \n
                          1. <\/b> Each group can receive privilege rules aligned with its actual administrative needs<\/span><\/li>\n
                          2. <\/b> EPM supports only one policy per endpoint<\/span><\/li>\n
                          3. <\/b> Every group must use different operating systems<\/span><\/li>\n
                          4. <\/b> Separate policies disable monitoring<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. Each group can receive privilege rules aligned with its actual administrative needs<\/b><\/p>\n

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

                            Different job functions need different endpoint privileges. Developers may require elevation for compilers or development tools, help-desk personnel may need approved administrative utilities, while ordinary office users may need little or no elevation. Applying one broad policy to everyone either grants excessive privilege or creates unnecessary friction. Role-specific policies allow organizations to enforce least privilege more precisely. This also simplifies auditing because administrators can explain why each group receives its particular endpoint privileges and can review those requirements independently.<\/span><\/p>\n

                            Question 314. Which approach is BEST when an administrator must create an EPM exception for a legacy application?<\/b><\/p>\n

                              \n
                            1. <\/b> Exempt all applications from control<\/span><\/li>\n
                            2. <\/b> Define the narrowest exception necessary and document the business reason and scope<\/span><\/li>\n
                            3. <\/b> Make every user a local administrator<\/span><\/li>\n
                            4. <\/b> Disable the EPM agent<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 3. Define the narrowest exception necessary and document the business reason and scope<\/b><\/p>\n

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

                              Legacy software sometimes requires unusual privileges, but exceptions should remain tightly controlled. The administrator should identify the specific executable, users, endpoints, and privileges involved, then create only the minimum policy exception needed for the application to function. The reason and owner should be documented so the exception can be reviewed later and removed when the application is upgraded or retired. Broad exemptions weaken application control and can create persistent privilege-escalation opportunities. Good EPM governance treats exceptions as managed technical debt rather than permanent defaults.<\/span><\/p>\n

                              Question 315. Why should EPM policies be periodically reviewed even if no users report problems?<\/b><\/p>\n

                                \n
                              1. <\/b> Endpoint software, roles, threats, and business requirements change over time<\/span><\/li>\n
                              2. <\/b> EPM automatically expires every policy daily<\/span><\/li>\n
                              3. <\/b> Review is required only to create PSM recordings<\/span><\/li>\n
                              4. <\/b> Policies cannot operate for more than one month<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 4. Endpoint software, roles, threats, and business requirements change over time<\/b><\/p>\n

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

                                A policy that was appropriate six months ago may now be unnecessarily broad or may no longer cover newly introduced applications. Users change roles, software versions change, legacy applications are retired, and threat techniques evolve. Periodic review helps remove obsolete elevation rules and confirm that current privileges still match business requirements. It also gives administrators an opportunity to tighten rules that were initially created during deployment or troubleshooting. Least privilege is therefore an ongoing governance process rather than a one-time implementation project.<\/span><\/p>\n

                                Question 316. What is the best reason to monitor privileged endpoint events after a new policy is deployed?<\/b><\/p>\n

                                  \n
                                1. <\/b> To verify that the policy is producing the intended security result without disrupting legitimate workflows<\/span><\/li>\n
                                2. <\/b> To disable all alerts<\/span><\/li>\n
                                3. <\/b> To generate target-system passwords<\/span><\/li>\n
                                4. <\/b> To create Safe members<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. To verify that the policy is producing the intended security result without disrupting legitimate workflows<\/b><\/p>\n

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

                                  Post-deployment monitoring confirms whether the policy behaves as designed. Administrators can identify legitimate applications being blocked, unexpected elevation requests, or risky activity that the policy successfully prevented. This feedback supports tuning and validates that security objectives are being achieved without excessive operational impact. CyberArk EPM Administration training includes both policy configuration and monitoring because enforcement without visibility makes troubleshooting difficult and can allow either hidden security gaps or unnoticed business disruption.<\/span><\/p>\n

                                  Question 317. What is the PRIMARY risk of granting users permanent local administrator rights as a workaround for repeated EPM policy issues?<\/b><\/p>\n

                                    \n
                                  1. <\/b> It creates broad standing privilege that can be abused by malware or compromised identities<\/span><\/li>\n
                                  2. <\/b> It improves least privilege too much<\/span><\/li>\n
                                  3. <\/b> It makes application troubleshooting impossible<\/span><\/li>\n
                                  4. <\/b> It prevents all software installation<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 4. It creates broad standing privilege that can be abused by malware or compromised identities<\/b><\/p>\n

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

                                    Permanent local administrator membership defeats the core objective of endpoint privilege management. Instead of fixing a narrowly scoped application or policy issue, it grants the user broad rights to modify the operating system, install software, alter security settings, and perform other privileged actions continuously. If the user session is compromised, an attacker can inherit those privileges. The better approach is to troubleshoot and refine the EPM policy so the specific legitimate workflow receives the necessary elevation while unrelated activity remains constrained.<\/span><\/p>\n

                                    Question 318. A policy works correctly on most Windows endpoints but fails on one endpoint after an agent upgrade. What should the administrator investigate first?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Whether that endpoint’s EPM agent is healthy and correctly synchronized after the upgrade<\/span><\/li>\n
                                    2. <\/b> Whether every user should receive a new Safe<\/span><\/li>\n
                                    3. <\/b> Whether Privilege Cloud CPM should be restarted<\/span><\/li>\n
                                    4. <\/b> Whether MFA should be disabled<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 2. Whether that endpoint’s EPM agent is healthy and correctly synchronized after the upgrade<\/b><\/p>\n

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

                                      When a problem appears on one endpoint immediately after an agent change, the local agent state is the most relevant difference. Administrators should verify service health, policy synchronization, connectivity, version compatibility, and any endpoint-specific errors before changing a policy that still works elsewhere. This is a fundamental troubleshooting principle: start with the smallest shared cause consistent with the evidence. CyberArk’s EPM Administration curriculum explicitly covers agent deployment, monitoring, and troubleshooting because endpoint-specific agent health is a common operational concern.<\/span><\/p>\n

                                      Question 319. Which CyberArk University course most directly covers EPM architecture, agent deployment, policy configuration, monitoring, and troubleshooting?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Privileged Access Manager Self-Hosted Administration<\/span><\/li>\n
                                      2. <\/b> Credential Provider Administration<\/span><\/li>\n
                                      3. <\/b> Endpoint Privilege Manager Administration<\/span><\/li>\n
                                      4. <\/b> Certificate Manager Administration<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 1. Endpoint Privilege Manager Administration<\/b><\/p>\n

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

                                        CyberArk University currently offers Endpoint Privilege Manager Administration as a dedicated technical course. The published curriculum covers EPM architecture, getting started, configuration and policy, agent deployment, implementation phases, set administration, monitoring, and troubleshooting. This specialization reflects the fact that endpoint least privilege and application control require different operational knowledge from traditional PAM password rotation or PSM administration. CyberArk’s training catalog continues to list EPM Administration as a separate learning path within its identity-security portfolio.<\/span><\/p>\n

                                        Question 320. An organization wants to remove local administrator rights while allowing developers, support engineers, and standard users to receive different approved privileges with minimal disruption. Which approach BEST meets the requirement?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Give every user permanent local administrator membership<\/span><\/li>\n
                                        2. <\/b> Use one broad elevation rule for all executables<\/span><\/li>\n
                                        3. <\/b> Deploy EPM agents, create role-specific least-privilege policies, pilot them on controlled groups, monitor events, and refine exceptions before broad enforcement<\/span><\/li>\n
                                        4. <\/b> Disable application control and rely only on user training<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. Deploy EPM agents, create role-specific least-privilege policies, pilot them on controlled groups, monitor events, and refine exceptions before broad enforcement<\/b><\/p>\n

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

                                          A mature EPM deployment combines technical enforcement with staged operational rollout. Agents provide endpoint enforcement, while role-specific policies ensure each population receives only the privileges it actually needs. Piloting reduces disruption and allows administrators to identify legitimate applications before broad enforcement. Event monitoring then provides evidence about blocked activity, elevation requests, and possible policy gaps. Narrowly scoped exceptions can be added where justified without giving users standing administrator rights. CyberArk’s EPM curriculum reflects this lifecycle by covering architecture, policy, agent deployment, implementation phases, monitoring, and troubleshooting.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full CyberArk CPC-SEN Exam Dumps and Practice Test Dumps. Question 301. What is the PRIMARY purpose of an Endpoint Privilege Manager policy? To configure Privilege Cloud Safe ownership To define how applications and privileged actions should be handled on managed endpoints To rotate passwords stored in the Digital Vault To configure PSM connection components […]<\/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\/21368"}],"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=21368"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21368\/revisions"}],"predecessor-version":[{"id":21369,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21368\/revisions\/21369"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}