ronutz
← All study guides

CP-PingOne-DaVinci

Certified Professional - PingOne DaVinci

Part of Certified Professional - PingOne DaVinci

Independent study aid built from the public exam blueprint. Not affiliated with, authorized by, or endorsed by ping. Objectives are transcribed and mapped by hand, so this page may contain mistakes or may have fallen behind the vendor's current material: exam objectives, versions, numbering and availability all change without notice. Treat ping's own certification portal as the source of truth and verify against it before you book anything.

Section 1: Applications

Section 2: Flow Building

  • 2.01 Create and use subflows

    What to know:
    • Subflows package reusable steps behind input/output contracts
    • Flow Conductor connector invokes them
    • Version subflows independently of parents
    • Pass data via input schema, return via output nodes

  • 2.02 Describe common core connector functionality (HTTP, Challenge, Flow Conductor, Function, Code Snippet, Form, Annotation)

    What to know:
    • HTTP connector: outbound calls, custom headers, response parsing
    • Challenge connector for OTP-style verification steps
    • Function and Code Snippet: inline logic in sandboxed JS
    • Flow Conductor for subflow calls; Form/HTTP for user-facing pages
    On this site: HTTP Methods: The Verbs of the Web, HTTP Headers: The Anatomy of the Metadata
    Tools: curl-command-builder, http-request-translator

  • 2.03 Configure JSON schema

    What to know:
    • Input schema declares expected flow inputs and types
    • Validation happens at flow start against the schema
    • Downstream nodes reference schema fields as variables
    On this site: The JSON Grammar: Six Types and a Few Strict Rules
    Tools: json-formatter

  • 2.04 Manage multiple flow versions

    What to know:
    • Save creates a new flow version; deploy promotes it
    • Applications pin versions through the flow policy
    • Roll back by re-pointing the policy to a prior version

  • 2.05 Create and configure a connector instance

    What to know:
    • Connector instances carry per-environment credentials
    • Same connector, multiple instances (e.g. two HTTP targets)
    • Instance settings vs per-node settings

Section 3: Flow Use Cases

  • 3.01 Given a scenario, identify a registration flow by its elements

    What to know:
    • Registration signatures: attribute-collection form, uniqueness check, create-user node, verification step
    • Often ends with auto-login or verification email branch

  • 3.02 Given a scenario, identify a password reset flow by its elements

    What to know:
    • Password reset signatures: identify user, verify via OTP/email, set-new-password node
    • Failure branches back to identification
    On this site: Choosing a Password Hash

  • 3.03 Given a scenario, identify an authentication flow by its elements

    What to know:
    • Authentication signatures: credential prompt, verify against directory, MFA branch, token/redirect completion
    • Risk or device checks appear before success
    On this site: The OIDC Authorization Code Flow, OAuth 2.0 yetkilendirme kodu akışı
    Tools: oauth-flow-chooser

Section 4: Managing and Debugging Flows

  • 4.01 Given a scenario, explain the troubleshooting process

    What to know:
    • Reproduce first: exact inputs and app context
    • Isolate the failing node via analytics trail
    • Check connector instance credentials and external endpoints
    • Compare against the last known-good version

  • 4.02 Given a scenario, explain the process for debugging flows during development

    What to know:
    • Flow Analytics: per-execution node trail with inputs/outputs
    • Debug mode in the flow studio with test inputs
    • Variable inspection at each node hop

Section 5: Data Management

Section 6: End-User UI

  • 6.01 Use external HTML, CSS, and JavaScript in flows

    What to know:
    • Custom HTML/CSS/JS on form-capable nodes
    • Assets constrained to the page sandbox
    • Keep logic in nodes; keep pages presentational
    On this site: CORS Explained: The Border Control of the Browser
    Tools: secure-headers

  • 6.02 Create user interface elements

    What to know:
    • Form fields, buttons, links composed per node
    • Field keys become flow data on submit
    • Validation and error display per element

  • 6.03 Integrate a flow policy into an application

    What to know:
    • Application widget or redirect launches the policy's flows
    • Embed via the DaVinci widget snippet with app credentials
    • Completion hands tokens/attributes back to the caller
    On this site: Açık ile gizli istemciler ve PKCE'nin yeri
    Tools: oauth-flow-chooser

  • 6.04 Build and apply DaVinci Forms

    What to know:
    • DaVinci Forms: reusable designed forms outside single nodes
    • Drag-and-drop fields with per-field validation
    • Attach forms to flows; submitted values land as flow data

Public sources, used in good faith

These guides are independent study aids built from publicly available material: published exam blueprints, official product documentation, and vendor training catalogues. Product names, exam codes, and trademarks belong to their owners and are used only to identify the subject being taught. This site is not affiliated with or endorsed by any vendor named here. If you hold rights in material published on this page and believe it should be removed or corrected, please send the exact URL and a short note on the issue through the contact page; requests are reviewed promptly and in good faith. Read the full disclaimer →