{"id":21350,"date":"2026-09-24T12:13:49","date_gmt":"2026-09-24T12:13:49","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=21350"},"modified":"2026-09-24T12:13:49","modified_gmt":"2026-09-24T12:13:49","slug":"cyberark-cpc-sen-practice-test-questions-and-exam-dumps-part7-q121-140","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cyberark-cpc-sen-practice-test-questions-and-exam-dumps-part7-q121-140\/","title":{"rendered":"CyberArk CPC-SEN Practice Test Questions and Exam Dumps Part7 Q121-140"},"content":{"rendered":"

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


\n<\/b>Question 121. What is the PRIMARY reason to duplicate an existing CyberArk platform before making significant configuration changes?<\/b><\/p>\n

    \n
  1. <\/b> To create a second copy of every managed account<\/span><\/li>\n
  2. <\/b> To preserve the original platform while allowing customized settings to be tested and applied separately<\/span><\/li>\n
  3. <\/b> To bypass CPM password management<\/span><\/li>\n
  4. <\/b> To create a new Privilege Cloud tenant<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. To preserve the original platform while allowing customized settings to be tested and applied separately<\/b><\/p>\n

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

    Duplicating a platform is a safer administrative approach when an organization needs account-management behavior that differs from an existing configuration. The duplicated platform can be customized without immediately changing the behavior of every account associated with the original platform. This reduces the risk of unintended credential-management failures and provides clearer rollback options. Administrators can test password rules, connection settings, reconciliation behavior, and other parameters against a limited account population before broader deployment. CyberArk administrator training treats policies and platforms as a core management area because platform configuration directly affects how privileged accounts are managed.<\/span><\/p>\n

    Question 122. What is the expected effect of deactivating a CyberArk platform?<\/b><\/p>\n

      \n
    1. <\/b> All accounts using the platform are immediately deleted<\/span><\/li>\n
    2. <\/b> Every Safe using the platform becomes inaccessible<\/span><\/li>\n
    3. <\/b> PSM recordings associated with the platform are erased<\/span><\/li>\n
    4. <\/b> The platform is prevented from being used for normal account management until it is reactivated<\/span><\/li>\n<\/ol>\n

      Correct Answer: 4. The platform is prevented from being used for normal account management until it is reactivated<\/b><\/p>\n

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

      Deactivating a platform is an administrative way to prevent that platform from being used for active account-management workflows without deleting the platform configuration itself. This can be useful when a platform is obsolete, undergoing changes, or should no longer be assigned to new accounts. Existing account relationships should be reviewed carefully before deactivation because managed accounts depend on their assigned platform for password-management behavior. Deactivation is therefore preferable to deletion when administrators may need to preserve configuration for review, migration, or possible later reactivation.<\/span><\/p>\n

      Question 123. Why should a CyberArk administrator avoid modifying a widely used platform without testing the change first?<\/b><\/p>\n

        \n
      1. <\/b> A platform change can affect password management for every account associated with that platform<\/span><\/li>\n
      2. <\/b> Platforms control only the Privilege Cloud portal theme<\/span><\/li>\n
      3. <\/b> Platform settings affect only PSM recordings<\/span><\/li>\n
      4. <\/b> Platform changes automatically disable MFA<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. A platform change can affect password management for every account associated with that platform<\/b><\/p>\n

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

        A platform defines the technical and policy behavior applied to the accounts associated with it. Changing password-generation rules, reconciliation settings, verification behavior, connection parameters, or related options can therefore affect a large account population at once. A configuration that works for one target may fail on another if the target systems enforce different password or authentication requirements. Administrators should test significant platform modifications with controlled accounts or a duplicated platform before applying them broadly. CyberArk training specifically emphasizes policies and platforms because these settings are central to PAM administration.<\/span><\/p>\n

        Question 124. What is the purpose of an account-level override in CyberArk?<\/b><\/p>\n

          \n
        1. <\/b> To replace the Digital Vault<\/span><\/li>\n
        2. <\/b> To bypass all Safe permissions<\/span><\/li>\n
        3. <\/b> To allow a specific managed account to use settings that differ from the platform defaults where supported<\/span><\/li>\n
        4. <\/b> To convert the account into an Identity Administration user<\/span><\/li>\n<\/ol>\n

          Correct Answer: 3. To allow a specific managed account to use settings that differ from the platform defaults where supported<\/b><\/p>\n

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

          Platform settings provide standardized management behavior for groups of similar accounts. Occasionally, one account requires an exception\u2014for example, a special password-management schedule, supporting account, address, or other account-specific property. An account-level setting or override can allow CyberArk to accommodate that exception without forcing administrators to create a completely different configuration for every minor variation. Overrides should be used sparingly because excessive exceptions make administration and troubleshooting more complicated. Standardized platform behavior is usually preferable unless the target account genuinely requires different handling.<\/span><\/p>\n

          Question 125. What is the PRIMARY benefit of assigning accounts to a platform that matches the target technology?<\/b><\/p>\n

            \n
          1. <\/b> CyberArk can use the appropriate password-management and connection behavior for that target type<\/span><\/li>\n
          2. <\/b> The account automatically becomes a Safe owner<\/span><\/li>\n
          3. <\/b> PSM no longer needs to authenticate the user<\/span><\/li>\n
          4. <\/b> CyberArk disables password verification<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. CyberArk can use the appropriate password-management and connection behavior for that target type<\/b><\/p>\n

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

            Different target technologies use different protocols, password rules, authentication methods, and management procedures. A Windows account, Linux account, database account, or application credential cannot always be managed correctly through identical technical settings. Assigning the correct platform lets CyberArk apply the appropriate CPM procedures, password rules, connection information, and related management behavior. Incorrect platform assignment is a common source of failed verification or password-change operations because CyberArk may attempt to interact with the target using assumptions that do not match the actual system.<\/span><\/p>\n

            Question 126. A CyberArk account is managed correctly, but one target requires a different reconciliation account from the platform default. What is the MOST appropriate approach?<\/b><\/p>\n

              \n
            1. <\/b> Disable reconciliation globally<\/span><\/li>\n
            2. <\/b> Delete the account and recreate it<\/span><\/li>\n
            3. <\/b> Give every user password-reset rights on the target<\/span><\/li>\n
            4. <\/b> Associate the appropriate reconciliation account specifically with that managed account where supported**<\/span><\/li>\n<\/ol>\n

              Correct Answer: 4. Associate the appropriate reconciliation account specifically with that managed account where supported<\/b><\/p>\n

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

              A platform can define default supporting accounts, but individual target accounts may require exceptions. If one account must be reset by a different reconciliation identity, associating the correct reconciliation account at the appropriate account level provides the needed flexibility without changing every other account on the platform. This preserves standardized behavior for the broader population while solving the exception cleanly. Reconciliation credentials should remain tightly protected because they have authority to reset other privileged passwords and therefore represent highly sensitive accounts themselves.<\/span><\/p>\n

              Question 127. Which CyberArk action is MOST appropriate before manually changing a managed password outside CyberArk during troubleshooting?<\/b><\/p>\n

                \n
              1. <\/b> Delete the Safe<\/span><\/li>\n
              2. <\/b> Understand the impact on synchronization and plan to Verify or Reconcile the account afterward<\/span><\/li>\n
              3. <\/b> Disable PSM permanently<\/span><\/li>\n
              4. <\/b> Remove the account’s platform<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. Understand the impact on synchronization and plan to Verify or Reconcile the account afterward<\/b><\/p>\n

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

                Changing a managed password directly on the target bypasses CyberArk’s credential-management workflow and can cause the value stored by CyberArk to become invalid. If such a manual change is unavoidable during troubleshooting, administrators should plan how CyberArk will regain synchronization. A Verify operation can detect that the stored password is no longer valid, while Reconcile can reset the target credential using an authorized reconciliation account. Uncontrolled out-of-band password changes should be avoided because they can interrupt applications, dependent accounts, and privileged-access workflows.<\/span><\/p>\n

                Question 128. What is the main purpose of CyberArk account activity or audit information?<\/b><\/p>\n

                  \n
                1. <\/b> To generate new target-system passwords<\/span><\/li>\n
                2. <\/b> To replace Safe permissions<\/span><\/li>\n
                3. <\/b> To provide a traceable record of important privileged account and administrative actions<\/span><\/li>\n
                4. <\/b> To automatically approve dual-control requests<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. To provide a traceable record of important privileged account and administrative actions<\/b><\/p>\n

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

                  Audit information provides accountability by recording significant actions involving privileged accounts and PAM administration. This can help determine who accessed an account, who modified permissions, when credential-management actions occurred, or which administrative changes were made. Audit data supports incident investigations, compliance reviews, troubleshooting, and segregation-of-duties oversight. CyberArk’s official PAM administration curriculum includes reports, system monitoring, common issues, and troubleshooting as core areas because operational visibility is essential to managing a privileged-access environment effectively.<\/span><\/p>\n

                  Question 129. What is the PRIMARY reason to review failed CPM operations in account activity rather than immediately forcing reconciliation?<\/b><\/p>\n

                    \n
                  1. <\/b> Reconciliation always deletes the account<\/span><\/li>\n
                  2. <\/b> Failed operations can reveal whether the real problem is connectivity, permissions, password policy, or supporting-account configuration<\/span><\/li>\n
                  3. <\/b> CPM failures can be resolved only by PSM<\/span><\/li>\n
                  4. <\/b> Account activity contains no troubleshooting information<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 4. Failed operations can reveal whether the real problem is connectivity, permissions, password policy, or supporting-account configuration<\/b><\/p>\n

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

                    Reconciliation is useful when the managed credential is genuinely unsynchronized, but it is not the correct response to every CPM error. A failed password change might instead result from target password complexity, insufficient permissions, network connectivity, or incorrect platform settings. Reviewing the failure details first helps administrators identify the actual layer at fault. Forcing reconciliation without understanding the error can fail for the same underlying reason or introduce additional changes to a sensitive account. Effective CyberArk troubleshooting starts with evidence and narrows the problem before remediation.<\/span><\/p>\n

                    Question 130. What is the BEST use of CyberArk reporting for privileged account governance?<\/b><\/p>\n

                      \n
                    1. <\/b> Reviewing privileged account inventory, activity, and management status for oversight and audit<\/span><\/li>\n
                    2. <\/b> Replacing target-system monitoring completely<\/span><\/li>\n
                    3. <\/b> Generating operating-system patches<\/span><\/li>\n
                    4. <\/b> Providing direct DNS services to connector servers<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. Reviewing privileged account inventory, activity, and management status for oversight and audit<\/b><\/p>\n

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

                      Reports help administrators and auditors understand the state of the privileged-access environment. They can be used to review account inventories, privileged activity, management status, and other information relevant to governance. Reporting complements live monitoring, PSM recordings, and operational logs; it does not replace them. A strong PAM program uses reports to identify unmanaged or problematic accounts, support periodic access reviews, demonstrate controls to auditors, and highlight areas requiring remediation. CyberArk’s administration training includes reporting as a dedicated topic.<\/span><\/p>\n

                      Question 131. Why is it important to periodically review Safe membership?<\/b><\/p>\n

                        \n
                      1. <\/b> To ensure users and groups still require the permissions they have been granted<\/span><\/li>\n
                      2. <\/b> To guarantee CPM changes every password immediately<\/span><\/li>\n
                      3. <\/b> To create new PSM connectors<\/span><\/li>\n
                      4. <\/b> To prevent CyberArk from generating reports<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 3. To ensure users and groups still require the permissions they have been granted<\/b><\/p>\n

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

                        Access requirements change when users move between roles, projects end, contractors leave, or administrative responsibilities change. If Safe membership is never reviewed, users can accumulate access they no longer need. Periodic review supports least privilege by confirming that current membership and assigned permissions remain appropriate. Group-based authorization can simplify this process, but group memberships themselves also require governance. Safe access reviews are especially important for high-value credentials because unnecessary permission to use or retrieve a privileged account increases the impact of an identity compromise.<\/span><\/p>\n

                        Question 132. An auditor needs to examine privileged-account activity but must not launch sessions or retrieve credentials. What is the BEST permissions strategy?<\/b><\/p>\n

                          \n
                        1. <\/b> Grant full Safe ownership<\/span><\/li>\n
                        2. <\/b> Grant only the minimum audit and visibility permissions required for the review<\/span><\/li>\n
                        3. <\/b> Grant Retrieve accounts but deny List accounts<\/span><\/li>\n
                        4. <\/b> Give the auditor the target passwords directly<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2. Grant only the minimum audit and visibility permissions required for the review<\/b><\/p>\n

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

                          An auditor generally needs evidence and visibility, not operational control over privileged accounts. CyberArk’s granular Safe permissions make it possible to provide audit-related access without granting the ability to use or retrieve credentials. This supports both least privilege and segregation of duties. Giving auditors broad Safe ownership would unnecessarily expand their capabilities and could compromise the independence of the audit function. Permissions should be tailored to what the auditor actually needs to inspect, such as account visibility and audit records.<\/span><\/p>\n

                          Question 133. What is the PRIMARY purpose of configuring an access-request expiration or limited timeframe?<\/b><\/p>\n

                            \n
                          1. <\/b> To restrict approved privileged access to the period in which it is actually needed<\/span><\/li>\n
                          2. <\/b> To permanently disable the privileged account afterward<\/span><\/li>\n
                          3. <\/b> To delete the user from CyberArk<\/span><\/li>\n
                          4. <\/b> To prevent CPM verification<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 4. To restrict approved privileged access to the period in which it is actually needed<\/b><\/p>\n

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

                            Time-bound access reduces standing privilege by limiting how long an approved user can exercise sensitive access. A user may have a legitimate reason to administer a system during a maintenance window but should not necessarily retain the same authorization afterward. Combining approval with a defined access period supports just-in-time principles and improves auditability. Time limits are especially valuable with dual control because the approver can authorize access for a specific business need rather than granting an open-ended privilege that remains available indefinitely.<\/span><\/p>\n

                            Question 134. Which condition should be checked if a previously approved access request no longer lets a user connect?<\/b><\/p>\n

                              \n
                            1. <\/b> Whether the approved timeframe has expired or the request conditions are no longer valid<\/span><\/li>\n
                            2. <\/b> Whether the account should be discovered again<\/span><\/li>\n
                            3. <\/b> Whether CPM should be uninstalled<\/span><\/li>\n
                            4. <\/b> Whether every Safe needs a new platform<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2. Whether the approved timeframe has expired or the request conditions are no longer valid<\/b><\/p>\n

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

                              Approval does not necessarily grant permanent access. CyberArk access requests can be limited by time and other request conditions. If a user previously connected successfully but later cannot use the same approval, administrators should confirm whether the authorized window has ended or the request has otherwise expired. This is different from a PSM failure or credential-management error. Troubleshooting should begin by checking the governance state of the request before making changes to connectors, accounts, or passwords.<\/span><\/p>\n

                              Question 135. Which CyberArk control MOST directly addresses the risk of users retaining powerful privileges after a temporary task is completed?<\/b><\/p>\n

                                \n
                              1. <\/b> Time-bound or just-in-time privileged access<\/span><\/li>\n
                              2. <\/b> Permanent Safe ownership<\/span><\/li>\n
                              3. <\/b> Shared administrator passwords<\/span><\/li>\n
                              4. <\/b> Disabling audit records<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1. Time-bound or just-in-time privileged access<\/b><\/p>\n

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

                                Time-bound and just-in-time access provide privileged capability only for the period in which it is required. This reduces standing privilege and therefore reduces the opportunity for attackers to abuse permanently elevated identities. CyberArk’s modern PAM approach increasingly includes just-in-time and Zero Standing Privilege models alongside traditional vaulted credentials. The objective is to make privilege temporary, controlled, attributable, and removable rather than allowing powerful rights to remain assigned indefinitely when they are not actively needed. CyberArk’s current certification catalog includes a Sentry Modern PAM study guide focused on contemporary PAM concepts.<\/span><\/p>\n

                                Question 136. What is the BEST reason to restrict account retrieval even when PSM session access is allowed?<\/b><\/p>\n

                                  \n
                                1. <\/b> Retrieved credentials can potentially be used outside the monitored CyberArk session path<\/span><\/li>\n
                                2. <\/b> PSM cannot connect if passwords remain hidden<\/span><\/li>\n
                                3. <\/b> Account retrieval is required for every session<\/span><\/li>\n
                                4. <\/b> Password retrieval automatically rotates the account<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. Retrieved credentials can potentially be used outside the monitored CyberArk session path<\/b><\/p>\n

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

                                  When users retrieve an actual password, they may be able to use that credential outside the PSM-controlled session workflow, depending on network and target access. This can reduce monitoring coverage and increase credential exposure. If users only need to perform administrative work, allowing them to use the account through PSM without retrieving the password is generally more secure. Retrieval permission should therefore be reserved for legitimate use cases where disclosure of the credential is operationally necessary, and such usage should remain auditable.<\/span><\/p>\n

                                  Question 137. A user can launch a PSM session but cannot retrieve the account’s password. What does this demonstrate?<\/b><\/p>\n

                                    \n
                                  1. <\/b> CyberArk can separate account usage from credential disclosure<\/span><\/li>\n
                                  2. <\/b> CPM is not managing the account<\/span><\/li>\n
                                  3. <\/b> The Safe is misconfigured<\/span><\/li>\n
                                  4. <\/b> PSM is bypassing authorization<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 2. CyberArk can separate account usage from credential disclosure<\/b><\/p>\n

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

                                    One of the fundamental benefits of PAM is allowing administrators to perform privileged tasks without necessarily learning the underlying password. Safe permissions distinguish between account usage and credential retrieval, while PSM can inject or use the credential during a brokered session. This reduces the chance that users copy passwords, store them locally, or reuse them through unmonitored access paths. The ability to launch a session without retrieving the password is therefore expected and desirable in many high-security CyberArk designs.<\/span><\/p>\n

                                    Question 138. Which situation BEST justifies temporarily disabling automatic password management for one account rather than the whole platform?<\/b><\/p>\n

                                      \n
                                    1. <\/b> A single target is undergoing maintenance and its credential must remain unchanged temporarily<\/span><\/li>\n
                                    2. <\/b> All targets using the platform require permanent password rotation<\/span><\/li>\n
                                    3. <\/b> The organization wants to remove all Safes<\/span><\/li>\n
                                    4. <\/b> PSM recording is unavailable<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 1. A single target is undergoing maintenance and its credential must remain unchanged temporarily<\/b><\/p>\n

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

                                      If only one account has a temporary business reason not to be rotated, changing the entire platform would affect many unrelated accounts. Account-level suspension of automatic management is therefore more targeted. The administrator should document the reason, limit the exception duration, and re-enable management when maintenance ends. Long-term disabled management creates risk because the account may stop receiving normal password verification and rotation. CyberArk’s account lifecycle controls are intended to let administrators handle exceptions without weakening the broader platform configuration.<\/span><\/p>\n

                                      Question 139. What should an administrator do after re-enabling automatic management on an account whose password may have been changed outside CyberArk?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Assume CyberArk and the target are synchronized<\/span><\/li>\n
                                      2. <\/b> Review synchronization and perform Verify or Reconcile as appropriate<\/span><\/li>\n
                                      3. <\/b> Delete all PSM recordings<\/span><\/li>\n
                                      4. <\/b> Remove the account from its Safe<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 4. Review synchronization and perform Verify or Reconcile as appropriate<\/b><\/p>\n

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

                                        While automatic management is disabled, someone may alter the target credential manually. Re-enabling management does not guarantee that CyberArk’s stored value still matches the target. The administrator should therefore validate synchronization. Verify can determine whether the stored credential is still valid, while Reconcile can restore control if CyberArk no longer has the correct current password. Checking synchronization before resuming normal rotations prevents repeated management failures and reduces the chance of disrupting dependent applications or privileged-access workflows.<\/span><\/p>\n

                                        Question 140. A CyberArk environment has one account that requires a unique reconciliation identity, auditors who must review activity without using accounts, and administrators who should connect through PSM without seeing passwords. Which design BEST meets these requirements?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Give all users full Safe ownership and Retrieve accounts permission<\/span><\/li>\n
                                        2. <\/b> Put every account in a separate CyberArk tenant<\/span><\/li>\n
                                        3. <\/b> Configure the account-specific reconciliation relationship, give auditors limited audit permissions, and grant administrators only the usage permissions and PSM connection methods needed for brokered access<\/span><\/li>\n
                                        4. <\/b> Disable CPM and PSM for the Safe<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. Configure the account-specific reconciliation relationship, give auditors limited audit permissions, and grant administrators only the usage permissions and PSM connection methods needed for brokered access<\/b><\/p>\n

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

                                          The scenario requires three distinct controls rather than one broad permission model. The special account should use the reconciliation identity required by its target environment without changing every other account on the platform. Auditors should receive only the visibility and audit rights needed for independent review. Operational administrators should be able to use the privileged account through PSM while credential-retrieval permission is withheld where unnecessary. This design applies least privilege, segregation of duties, controlled credential recovery, and monitored session access simultaneously\u2014the core operational principles emphasized throughout modern CyberArk PAM administration.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full CyberArk CPC-SEN Exam Dumps and Practice Test Dumps. Question 121. What is the PRIMARY reason to duplicate an existing CyberArk platform before making significant configuration changes? To create a second copy of every managed account To preserve the original platform while allowing customized settings to be tested and applied separately To bypass CPM […]<\/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\/21350"}],"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=21350"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21350\/revisions"}],"predecessor-version":[{"id":21351,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/21350\/revisions\/21351"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=21350"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=21350"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=21350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}