Pegasystems PEGAPCDS80V1_2020 Exam Prep
Pega Certified Data Scientist (Page 4 )

• C: Develop the rule in the Rules Editor, define the events, match, and condition sections, then use the test rule feature. This directly validates the YARA-L rule without enabling it in production.
• A: UDM Search can help investigate data and refine filters, but it does not fully test YARA-L logic—especially complex event joins, match windows, and conditions.

• Disable high concurrency: This changes session-sharing behavior but does not provide dedicated compute or true workload separation.
• Modify the number of executors: Adjusts resources within a Spark job; it does not isolate bronze and silver processes.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• A. Continue using the current system: It will eventually fail and offers no recovery strategy.
• B. Virtualize the entire system: Correct. A VM can preserve the old OS, application, settings, and dependencies while running on newer physical hardware.
• C. Containerize the application: Containers generally share the host OS kernel and are not suitable for preserving an entire incompatible legacy OS.
• D. Clone the disks to USB: A disk clone may provide backup or temporary recovery, but it does not solve hardware compatibility or provide a reliable long-term platform.

• GPS coordinates
• Date and time the image was taken
• Camera or device information
• Image dimensions and software used

• Log data: Records generated by systems or applications, not normally embedded in image files.
• Encrypted data: Information intentionally encoded to prevent unauthorized access.
• Sensitive data: A broad classification, not the specific type of information being extracted.

• D — Value analysis: Correct. It examines an existing product to identify ways of reducing its cost while still providing the required functions, quality and reliability.
• E — Kaizen costing: Correct. It involves making continuous, small improvements and cost reductions while the product is already in production.

• Functional analysis: It is not limited to minimizing the cost of the originally defined functions. It examines what functions are required and how they can be provided at the lowest overall cost.
• Value engineering: Usually applies to the design and development of a new product, rather than being a fundamental redesign of existing organisational processes. That description is closer to business process re-engineering.
• Target costing: The target cost is generally established during the product development stage, before production begins. It is not continuously reset while the product is in production.

• The vulnerability scan identifies a vulnerability.
• The administrator verifies that the vulnerability is not present.
• Therefore, the scan produced a false positive.

• True positive: A vulnerability is reported and genuinely exists.
• False negative: A vulnerability exists, but the scan fails to detect it.
• True negative: No vulnerability exists, and the scan correctly reports no issue.

• Fine-tuning requires a properly formatted training dataset.
• For classification or instruction-style fine-tuning, examples are supplied in JSONL format.
• Each line represents one training example, typically containing the input prompt and the desired completion or label.
• The file must then be uploaded or made available to the Microsoft Foundry fine-tuning workflow.

• A: Prompt Flow is useful for prompt experimentation, but it is not required to start fine-tuning.
• B: You do not need to deploy the base model to an online endpoint before fine-tuning.
• C: Tracing supports observability and evaluation, but it does not prepare the fine-tuning job or dataset.

• Wireshark captures packets and allows you to examine their contents, potentially revealing usernames and passwords sent without encryption.
• Netcat creates network connections and can send or receive data, but it is not primarily a packet-analysis tool.
• Nessus scans for known vulnerabilities and configuration issues; it generally would not prove that credentials are visible in transit.
• Nmap performs network discovery and port/service scanning, not detailed packet-content inspection.

• Malware or malicious software
• Command-and-control tools
• Internet surveillance and intrusion software

• ITAR: A U.S. regulation controlling defense-related articles and services; it is not the international arrangement described.
• Palermo Convention: Focuses on transnational organized crime and related protocols, not export controls for cyber weapons.
• GDPR: European data-protection and privacy legislation.

• Sales process: Controls which Opportunity Stage values are available.
• Record type: Associates the appropriate sales process with a business scenario and controls available picklist values.
• Page layout: Controls which fields are displayed and whether they are required or read-only.

• Energy Market Team 1 ? Record Type 1, Sales Process 1, Page Layout 1
• Energy Market Team 2 ? Record Type 2, Sales Process 2, Page Layout 2
• Services/Installation Team ? Record Type 3, Sales Process 3, Page Layout 3

Manager role

DAX 
Country[Manager] = USERPRINCIPALNAME()

• Sales
• Human Resources

CFO role

• See sales for all countries
• See no Human Resources data

• Do not restrict the Country table or Sales table.
• Apply a filter to Human Resources that always returns false, such as:

DAX 
FALSE()

• Response and resolution time frames
• Availability or uptime requirements
• Performance targets
• Support obligations
• Penalties for failing to meet requirements

• SOW (Statement of Work): Defines the project’s scope, tasks, and deliverables.
• MOA (Memorandum of Agreement): Describes cooperation and responsibilities between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, usually without detailed enforceable service targets.

• MFA adds an additional authentication factor, such as a phone notification or verification code.
• It helps prevent unauthorized sign-ins, even if a password is compromised.
• It does not encrypt, store, or protect credentials used by deployment processes.

• Constrained VMs: VMs whose workloads are experiencing resource pressure, such as insufficient CPU or memory. They may need additional resources or optimization.
• Overprovisioned VMs: VMs allocated more CPU, memory, or storage than their workloads require. Their resources may be reclaimed or reduced.

• Underprovisioned VMs: This is not the predefined view identified for this report question.
• Zombie VMs: These are typically inactive or unused VMs and are useful for cleanup, but they are not the two views specifically intended here to identify inefficient resource allocation.

• A. IDS attack signatures: Detects suspicious network activity, but is not primarily designed to scan uploaded files for malware.
• C. Load balancer: Distributes traffic among servers and improves availability; it does not inspect files for threats.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection, but its primary role is not malware scanning of uploaded documents.

1. x = -100
2. -100 < x < 100
3. 100 = x < 1000
4. x = 1000

• -500 ? class 1
• 0 ? class 2
• 100 ? class 3
• 1000 ? class 4

• Assign endpoints to a group based on the result of one policy.
• Use that group as the scope of another policy.
• This effectively passes the endpoints from one policy’s processing flow to another.

• When the MVP will be defined — the MVP should already be understood sufficiently when assessing the business case.
• What the MVP is — useful information, but not the key requirement tested here.
• That the MVP is the same as project viability — incorrect. The MVP helps test viability; it is not identical to viability itself.

• PC A: 192.168.1.10/24
• PC B: 192.168.2.10/24

• Both PCs have a correct default gateway
• A router or Layer 3 switch connects the subnets
• Routing and firewall rules allow the traffic

• A PostToolUse hook for file writes under src/api/ that runs the linter.
• A separate PostToolUse hook for API/data processing that normalizes payloads to snake_case.

• Frequency/likelihood = how often or how likely the risk is to occur.
• Severity/impact = how damaging or costly the consequences would be.

• A minor equipment fault occurring frequently may have high frequency but low severity.
• A major cyberattack occurring rarely may have low frequency but high severity.
• A risk that happens often and causes substantial losses has high frequency and high severity.

• Design Studio > Emails ? create an email-template folder
• Design Studio > Landing Pages ? create a landing-page-template folder
• Add the relevant assets to each folder
• Right-click the folder and choose Share Folder
• Select the destination workspaces

• Injection
• Broken access control
• Authentication failures
• Security misconfiguration
• Cross-site scripting

• STIX: A standardized language and format for exchanging threat intelligence.
• OVAL: Used to describe and assess system vulnerabilities and configuration issues.
• Threat intelligence feed: Provides current indicators and intelligence about threats, but not necessarily a structured overview of common application exploitation methods.
• CVE: A catalog of individually identified, publicly disclosed vulnerabilities.

• Who owns security risks and decisions
• Who is responsible for implementing controls
• Who reports security performance to management
• How security responsibilities align with business objectives

• B — Compliance with audit requirements: Governance may support compliance, but audit compliance is not its main objective.
• C — Monitoring security incidents: This is an operational security activity, not the central purpose of governance.
• D — Creation of tactical solutions: Governance establishes direction and oversight; tactical solutions belong to management and operational teams.

• Label applied does not automatically exclude a file from Copilot.
• Encryption/usage rights determine whether Copilot can access the file’s content.
• If the user has no permission under Label2, File3 should be unavailable to Copilot for that user.
• File3’s label might be inherited by derived content only if File3 was actually processed and contributed by an authorized user; it should not be treated as contributing merely because it exists in the source set.

• SOSL searches text across objects and is not appropriate for selecting Account table columns.
• describeSObjects() provides metadata about objects and fields, but it does not itself build or execute the query.
• Dynamic Schema binding supports runtime determination of object and field information, which is required here.
• REST API is unnecessary because this is being implemented in Apex.

• The ERSPAN source is the device or interface whose traffic is being copied.
• The ERSPAN destination is the device receiving the encapsulated copy and forwarding it to the traffic analyzer.
• The local monitor session number is locally significant. Therefore, the source and destination do not need matching session IDs such as 47 or 48.
• The erspan-id identifies the ERSPAN stream and must correspond between the source and destination configuration.

• Bronze: Raw ingested data
• Silver: Cleaned, validated, and transformed data
• Gold: Business-level data for analytics, dashboards, and reporting

• Behavioral and anomaly detection
• Threat intelligence integration
• User and entity behavior analytics
• Automated response actions, often through SOAR integration

• Virus signatures: Associated primarily with antivirus or endpoint protection.
• Security agent deployment: Usually an endpoint-management or EDR function.
• Vulnerability scanning: Typically performed by vulnerability-management tools, though a SIEM may integrate their results.

• /27 (255.255.255.224)

• /26 (255.255.255.192)

• /25: Creates only 2 subnets, not 3
• /28: Provides only 14 usable hosts per subnet