DSPM- Deploy-and-Administer Certified Forcepoint DSPM - Professional: Deploy and Administer Exam Questions and Answers

Click EDIT WIDGETS in the upper-right area of the dashboard.

Ella should click the EDIT WIDGETS button near the upper-right side of the dashboard, beside the EXPORT PDF button. This control opens the dashboard edit view, which exposes the controls required to modify dashboard content, including adding widgets and adding panels. In the screenshot, the correct click target is the green-outlined EDIT WIDGETS button above the dashboard panels.

Forcepoint documents dashboards as being primarily constructed from panels and widgets . A panel is the container that organizes one or more widgets, while widgets display selected datasets such as files, trustees, connectors, agents, or other DSPM analytics data. The Forcepoint documentation specifically states: “Edit Widgets: Click the Edit Widget button, to open the edit view.” It then lists Add widget and Add panel as functions available from that edit mode.

Therefore, Ella cannot add a panel by clicking the existing charts, the left navigation list, or the dashboard title. She must first enter edit mode through EDIT WIDGETS , then use the available Add panel option. References/topics: Analytics, Components of a Dashboard, Edit Widgets, Add Panel, Panels and Widgets .

Forcepoint DSPM pattern matching is used to identify defined pieces of information inside scanned content by applying regular expressions. The documented function is discovery and classification: pattern matching identifies particular information in a document by using RegEx that attempts to match file content. This makes identifying personally identifiable information on SharePoint the correct use case. SharePoint is a supported Microsoft data source for scanning, and Forcepoint specifically documents SharePoint Online as a connector used to scan SharePoint accounts and apply classification tags to files containing sensitive data stored in SharePoint.

The key distinction is that pattern matching does not perform remediation actions such as redaction or encryption. Options B and D therefore overstate the capability: Forcepoint DSPM may discover and classify sensitive data that later informs controls, but the pattern itself is not a redaction or encryption engine. Option A is less precise in this context because the question is testing the canonical pattern-matching use case against scanned documents and repositories, while the strongest documented repository example among the choices is SharePoint. Pattern configuration can also assign classification, compliance, and distribution tags when a RegEx is detected, such as GDPR/PII tagging for identifiers. References/topics: Pattern Matching, RegEx, Compliance Tags, SharePoint Scanning, Sensitive Data Classification .

The correct answer is C. Data Mapping . In Forcepoint DSPM, Security Posture Policies are used to define and govern critical business data assets, often referred to as crown-jewel data. Each policy represents a managed data asset associated with a department, owner, and query-based definition. The Data Mapping field is where the administrator enters or edits the GQL query that identifies which files or records belong to that data asset. Forcepoint’s documentation explicitly lists Asset Name , Department , Data Owner , and Data Mapping as required Security Posture Policy details, and defines Data Mapping as “a GQL query used to identify the data asset within the DSPM database.”

This distinction matters because Asset Name is only the business label, Department assigns responsibility to a business unit, and Data Owner identifies the person or group accountable for monitoring and compliance. The actual technical selection logic is contained in Data Mapping , where GQL can match data across sources such as SMB and SharePoint using query criteria like source and path. References/topics: Policy Center, Data Register, Security Posture Policies, Data Mapping, GQL, Data Asset Inventory .

The correct answer is B . In Forcepoint DSPM, content detectors analyze file contents using configured search logic such as keywords, phrases, positive and negative terms, or regular expressions. During detector creation, administrators can associate the detector with a detector group. Forcepoint states that when a detector group is selected, the detector becomes part of the AI Mesh and contributes to classification results. If the administrator does not want the detector to influence classification, a non-AI Mesh detector group should be selected instead.

This is important because detector grouping controls whether detector hits are merely informational or actively influence classification decisions. A payroll detector, for example, may search for terms such as salary, payslip, compensation, or payroll. If tied into the AI Mesh, those hits can help classify files as sensitive or confidential. The other options misrepresent detector behavior. Detectors do not automatically revoke permissions, convert keywords directly into taxonomy labels, or disappear from scan results when grouped. References/topics: Administration > Detectors, Content Detectors, Detector Groups, AI Mesh, Classification Results, Contain/Not Contain Logic .

Select the Actions drop-down in the upper-right corner of the LDAP provider screen, then choose Sync all users or Sync changed users .

Manual synchronization is initiated from the LDAP provider configuration page inside Keycloak User Federation, not from the general DSPM dashboard or from the Users page. The correct UI location is the Actions menu at the upper-right of the LDAP provider screen. In the screenshot, this is the open drop-down containing options such as Sync all users , Sync changed users , Unlink users , and Remove imported . To force synchronization after a successful connection test, choose Sync all users for a full import or Sync changed users when only deltas are required.

Forcepoint DSPM uses Keycloak for Active Directory import. The official DSPM documentation states that AD users are added through Keycloak , with administrators selecting the gv realm, navigating to User Federation , and adding/configuring an LDAP provider. It also identifies synchronization settings such as Import users , Periodic full sync , and Periodic changed users sync as the mechanisms used to bring LDAP users into Keycloak and then into DSPM.

Therefore, the click target is the upper-right Actions drop-down on the LDAP provider page , specifically the sync command within that menu. References/topics: User Federation, LDAP Provider, Active Directory Import, Keycloak gv Realm, Synchronization Settings .

The correct selections are Revoking user permissions , Exporting reports , and Manually verifying ML classification . The Enterprise Search page is the primary file-level investigation view in Forcepoint DSPM. It lists scanned and cataloged files, allows filtering through standard filters or GQL, and provides operational actions against the returned results. Forcepoint states that Enterprise Search allows users to filter file data, save frequently used filters, customize columns, and generate meaningful reports. It also provides an EXPORT button that creates a CSV or JSON download of the filtered data.

Revoking permissions is also supported as a data-governance action. Forcepoint documents that administrators can view or modify file permissions and access rights from the file Actions menu, and supporting documentation identifies required permissions for revoke operations in Microsoft repositories.

Manual classification validation is explicitly available from the Enterprise Search hamburger menu. Forcepoint states that to adjust a file’s machine-learning classification, the user selects Manually verify classification , modifies the ML-suggested classification, and saves the change.

The incorrect choices are outside this specific Enterprise Search action set. Moving risky files to a private folder is not the standard named Enterprise Search action in this workflow, and assigned risk is not manually changed from the page. References/topics: Enterprise Search, Exporting Data, Permissions & Access Rights, Manual ML Classification Verification .

The correct answer is D. Enhances data security . In Forcepoint DSPM, taxonomy is the structured classification model used to assign sensitivity meaning to discovered data. Forcepoint describes taxonomy as a machine-learning-based structured classification system that assigns sensitivity levels such as Confidential , General Business , Public , and Highly-Confidential . This classification directly corresponds to the Classification column in scan results, allowing security and governance teams to understand how sensitive a file or data asset is after scanning.

A custom taxonomy improves security because it lets an organisation align DSPM classification labels with its own internal data-handling rules, security protocols, and business language. Forcepoint notes that taxonomy customization ensures data handling aligns with an organisation’s security protocols, and that applied tags are visible in the Data Asset Inventory . In the administration taxonomy workflow, Forcepoint also explains that predefined AI Mesh tags can be supplemented with custom tags for pattern matching and detection rules, and those tags can be mapped to data-source taxonomies for label writeback.

The other options describe possible operational goals but not the primary purpose of taxonomy. Taxonomy is not an authentication mechanism, deduplication feature, or storage-reduction tool. References/topics: Taxonomy, Classification Tags, AI Mesh, Pattern Matching, Data Asset Inventory, Compliance Hub .

Path Detectors = Monitor storage locations of sensitive data

Content Detectors = Analyze data within files for sensitive data

Attribute Detectors = Identify meta-data within documents

Forcepoint DSPM separates detector logic into path, content, and attribute-based functions so classification can be driven by where data is stored, what the file contains, and what scan-derived attributes describe the file. Path Detectors evaluate file path information, including directory location, filename, and extension. Forcepoint describes them as identifying and classifying files based on directory location and file extensions, which aligns with monitoring storage locations where sensitive data resides.

Content Detectors inspect the actual contents of files. Forcepoint states that content detectors analyze file content and categorize based on keywords, phrases, positive and negative terms, or patterns, making them the correct match for analyzing data within files for sensitive data.

Attribute Detectors operate on scan-result attributes rather than raw text content alone. Forcepoint describes them as defining criteria for “critical” and “sensitive” based on attributes in scan results, including ML output or path/content detector hits. This maps most closely to identifying metadata or scan-derived characteristics within documents. References/topics: Detectors, Path Detectors, Content Detectors, Attribute Detectors, AI Mesh, Classification Model .

The correct answer is A . Forcepoint DSPM pattern matching is designed to let administrators define and tune custom detection logic for organisation-specific sensitive data. The documented pattern-matching function identifies particular information in documents by using Regular Expressions , and Forcepoint notes that pattern matching uses Golang RegEx syntax, which is separate from Detector syntax.

When a new pattern is added under Administration > Pattern Matching , the configuration includes Pattern Name , Regular Expression , enablement state, hidden RegEx handling, and tag assignments for Classification , Compliance , and Distribution . Forcepoint states that the Regular Expression is “the sequence to be matched,” and that selected tags can override machine-learning model output during endpoint suggestions and file scans. This supports the principle that custom patterns can be adjusted so the RegEx better matches an organisation’s data formats, identifiers, project codes, or regulatory artifacts.

The other statements do not match the documented pattern workflow. Country assignment is not presented as a core custom-pattern field. Export/import of data patterns is not part of the stated pattern-matching configuration flow. Default or preconfigured patterns are provided as built-in detection content and should not be treated as administrator-editable RegEx templates. References/topics: Pattern Matching, Add New Pattern, RegEx, Classification Tags, Compliance Tags, Distribution Tags .