Todos os guias de estudo

CP-PingDirectory

Certified Professional - PingDirectory

Parte de Certified Professional - PingDirectory

Proctored exam; no prerequisites. Official recommended training: Introduction to PingDirectory; Getting Started With PingDirectory; PingDirectory Administration Training.

Material de estudo independente, construído a partir do blueprint público da prova. Sem afiliação, autorização ou endosso da ping. Os objetivos são transcritos e mapeados à mão, então esta página pode conter erros ou estar defasada em relação ao material atual do fabricante: objetivos, versões, numeração e disponibilidade mudam sem aviso. Trate o portal de certificação da própria ping como a fonte da verdade e confira nele antes de agendar qualquer coisa.

Section 1: Installation and Initial Configuration

  • 1.01 Identify the system requirements.

    O que saber:
    • Java 17+ runtime and supported OS baselines
    • File-descriptor and vm.max_map_count tuning
    • Memory sizing: DB cache vs JVM heap
    • Disk layout for db, logs, and changelog
  • 1.02 Describe how to install PingDirectory.

    O que saber:
    • setup tool: interactive vs non-interactive (--cli --no-prompt)
    • Initial root DN and base-entry creation
    • Listener ports: LDAP 389/636, HTTPS, JMX
    • dsstatus / server status verification after install
  • 1.03 Describe the product’s file system structure.

    O que saber:
    • bin/ and lib/ vs config/ vs db/ layout
    • config/config.ldif is generated - never hand-edit
    • logs/ family: access, errors, config-audit
    • bak/, ldif/, and locks/ working directories
  • 1.04 Demonstrate how to perform an upgrade of the product.

    O que saber:
    • update tool with the new package in place
    • --serverRoot pointing at the live install
    • Reversion support via revert-update
    • Replication-aware upgrade ordering (one server at a time)
  • 1.05 Describe the product’s data storage engine.

    O que saber:
    • Berkeley DB JE - log-structured append-only storage
    • Backends map suffixes to databases (userRoot)
    • DB cache percent and checkpointing behavior
    • Why compaction/cleanup runs in background threads

Section 2: Administrative Tools

  • 2.01 Describe the functionality of the administrative console.

    O que saber:
    • HTTPS administrative console served by the server itself
    • Console authenticates as a directory user with privileges
    • Status, monitoring, and config editing scopes
    • When the console writes, config-audit.log records it
  • 2.02 Describe the use purpose of various command-line utilities included with the product.

    O que saber:
    • ldapsearch / ldapmodify / ldapdelete for data
    • dsconfig for configuration, dsreplication for topology
    • import-ldif / export-ldif, backup / restore
    • collect-support-data, summarize-access-log, status
  • 2.03 Describe how to use the dsconfig command and its options to configure the PingDirectory server.

    O que saber:
    • Interactive menu mode vs single-command batch mode
    • --batch-file for repeatable, reviewable changes
    • Every dsconfig change is an LDAP mod under the covers
    • Offline vs online configuration considerations
  • 2.04 Describe how to review configuration changes.

    O que saber:
    • config-audit.log: every change, timestamped, with the reverting command
    • Comparing config.ldif snapshots across time
    • Who changed what: the authenticated identity is recorded
  • 2.05 Demonstrate how to update server profiles.

    O que saber:
    • Server profile = versionable directory of config, dsconfig batches, and setup arguments
    • manage-profile generate-profile / replace-profile
    • The GitOps pattern: profiles in source control
    • Variables files for per-environment differences

Section 3: Data Management

  • 3.01 Explain how to perform management tasks for entries.

    O que saber:
    • ldapmodify with LDIF change records (add/modify/delete/modrdn)
    • Schema enforcement on every write
    • Operational attributes: createTimestamp, modifiersName
    • Soft-delete and undelete capabilities
  • 3.02 Describe different data types and their uses.

    O que saber:
    • Attribute syntaxes: DirectoryString, Integer, GeneralizedTime, Boolean, DN
    • Matching rules drive comparison and indexing
    • userPassword storage schemes vs plain attributes
    • Binary attributes and ;binary transfer
  • 3.03 Describe how to import and export data.

    O que saber:
    • import-ldif rebuilds the backend (offline, fast, destructive)
    • export-ldif for full or filtered exports
    • --includeBranch / --excludeAttribute shaping
    • Compressed and encrypted LDIF handling
  • 3.04 Describe the use of the make-ldif template.

    O que saber:
    • make-ldif templates generate realistic sample data
    • Template variables, branches, and per-entry randomization
    • The bundled example.template as the starting point
    • Load-testing datasets without production data
  • 3.05 Explain how to create and manage indexes.

    O que saber:
    • Index types: equality, presence, substring, ordering, approximate
    • Unindexed searches: who may run them, and why they hurt
    • rebuild-index after adding or changing an index
    • Index entry limit and its exceeded-cost behavior
  • 3.06 Describe the different group types and their uses.

    O que saber:
    • Static groups (groupOfNames/member) vs dynamic groups (memberURL)
    • Virtual static groups bridge the two models
    • Nested membership and the isMemberOf virtual attribute
    • Group performance at scale: prefer dynamic where possible

Section 4: Maintenance

  • 4.01 Explain how to enable logging and create retention/rotation policies for logs.

    O que saber:
    • Log publishers: access, error, audit - independently configured
    • Rotation policies (size/time) vs retention policies (count/disk/age)
    • Filtered and JSON-formatted access logging
    • Sensitive-attribute redaction in logs
  • 4.02 Identify how to install an updated PingDirectory license.

    O que saber:
    • Licenses installed at setup or via dsconfig update
    • Expiration warnings surface in status and error logs
    • New license file replaces the old in place
  • 4.03 Define the purpose and use of the collect-support-data and summarize-access-log commands to generate a report for support purposes.

    O que saber:
    • collect-support-data bundles config, logs, and metrics for support
    • summarize-access-log turns raw access logs into a performance report
    • Unindexed-search and long-etime hunting starts here
  • 4.04 Explain how to configure backup/restore for backends manually.

    O que saber:
    • backup / restore per backend, online-capable
    • Incremental backups against a full base
    • Encrypted and compressed backup options
    • Restoring into a replicated topology: re-initialize after
  • 4.05 Define the purpose of lockdown mode and describe how to enter/exit it.

    O que saber:
    • Lockdown mode: only root users over loopback may bind
    • enter-lockdown-mode / leave-lockdown-mode tools
    • Automatic lockdown on serious errors (e.g. schema problems)
    • The safe room for repair work
  • 4.06 Describe how to configure replication and define topologies.

    O que saber:
    • dsreplication enable / initialize between servers
    • Replication is multi-master with per-attribute conflict resolution
    • Topology registry stores the server relationships
    • Monitoring: replication backlog and generation IDs

Section 5: Security

  • 5.01 Describe how to create, export, or import encryption settings definitions.

    O que saber:
    • Encryption-settings definitions with a preferred (active) key
    • export / import definitions to share across the topology
    • What gets encrypted: backends, backups, logs, LDIF
    • Key rotation: add new preferred, keep old for reads
  • 5.02 Explain how to create password validators and define policies.

    O que saber:
    • Password validators: length, character sets, dictionary, history, similarity
    • Password policies bind validators, lockout, and expiration together
    • Per-user policy assignment via ds-pwp-password-policy-dn
    • Deprecated vs allowed storage schemes on migration
  • 5.03 Explain how to use the different features to manage accounts and view password and account policy properties for users.

    O que saber:
    • manage-account: view and operate on a single account's state
    • Password/account state properties: locked, expired, disabled
    • Administrative resets vs self-change semantics
    • Account-status notifications for downstream systems
  • 5.04 Demonstrate knowledge of how root and topology users and privileges are managed.

    O que saber:
    • Root users live under cn=Root DNs,cn=config - not in userRoot
    • Privileges (bypass-acl, config-write, unindexed-search) are granted explicitly
    • Topology administrators span the whole replicated topology
    • Least privilege: task-specific admin accounts over one super-root
  • 5.05 Describe the usage of certificate stores.

    O que saber:
    • JKS and PKCS#12 key/trust stores wired via dsconfig
    • Key manager vs trust manager providers
    • Server certificate rotation without downtime
    • Client-cert (mutual TLS) trust configuration
    Ferramentas: x509

Section 6: Integrations

  • 6.01 Describe how to configure additional attributes for SCIM.

    O que saber:
    • SCIM 2.0 endpoint maps directory attributes to SCIM schemas
    • Custom attribute mappings extend the core user schema
    • Resource types and schema endpoints for discovery
  • 6.02 Describe the purpose and use case for PingDirectoryProxy.

    O que saber:
    • PingDirectoryProxy: entry balancing, load balancing, and failover in front of stores
    • Proxying transformations and request routing
    • When to proxy: partitioned data or heterogeneous backends
  • 6.03 Describe the purpose and use case for PingDataSync.

    O que saber:
    • PingDataSync: sync pipes between source and destination
    • Sync classes map and transform attributes in flight
    • Real-time change detection via changelog
    • Directory-to-directory and directory-to-database patterns

Fontes públicas, usadas de boa-fé

Estes guias são materiais de estudo independentes, montados a partir de conteúdo publicamente disponível: blueprints de exame publicados, documentação oficial de produto e catálogos de treinamento dos fabricantes. Nomes de produtos, códigos de exame e marcas pertencem a seus titulares e são usados apenas para identificar o assunto ensinado. Este site não é afiliado a nenhum fabricante aqui citado nem endossado por ele. Se você detém direitos sobre material publicado nesta página e entende que ele deve ser removido ou corrigido, envie a URL exata e uma breve nota sobre o problema pela página de contato; os pedidos são analisados com rapidez e boa-fé. Ler o aviso legal completo