Pegasystems PEGAPCBA87V1 Exam Prep
Certified Pega Business Architect (PCBA) 87V1 (Page 2 )

• la schermata completa della domanda 3;
• i log di ogni host;
• il log del firewall;
• la sezione Explanation, se disponibile.

• Atomicity: a write fully succeeds or does not appear.
• Consistency: table state remains valid.
• Isolation: concurrent operations do not corrupt one another.
• Durability: committed changes persist.

• Flexible schemas: common data lakes often support flexible or schema-on-read data.
• Open-source formats: common data lakes commonly use open formats such as Parquet.
• Scalable storage: cloud data lakes already provide scalable storage.

1. Which host originated the infection
2. Whether each other host is clean or infected
3. Which firewall or host logs provide evidence of the infection’s movement

• Find the earliest infection-related event. The host associated with that event is the likely origin.
• Follow the timeline: outbound connections from that host may indicate propagation or command-and-control activity.
• A host receiving suspicious traffic is not automatically infected; look for evidence that it executed or initiated malicious activity.
• A firewall log can show traffic paths, but endpoint logs are usually needed to confirm infection.
• Mark a host clean only when the logs show no indicators of compromise or malicious activity.

1. Write a structured log entry to CloudWatch Logs containing:

1. Create a CloudWatch Logs metric filter that:

text 
ApiRequests 
Operation=GetOrders 
ResponseCode=500 
Version=2.4.0

• B is incorrect: CloudWatch Logs Insights queries analyze logs but do not directly publish metrics in this manner.
• C is incorrect: ALB access logs do not contain arbitrary Lambda response metadata as custom fields.
• D is incorrect: X-Ray traces and insights are not the appropriate mechanism for creating these custom, dimensioned application metrics.

• Marketing users: Dynamic Forms can show all fields.
• Support users: Field visibility rules can display only the Support preference fields on the record page.
• Reporting: Both profiles can still report on all fields because Dynamic Forms controls page visibility, not the underlying field access.

• A — Two record types and page layouts: Page layouts can control field placement and editability, but they are less flexible for conditional field visibility and would not be the best fit here.
• C — Muting permission set: Permission-set muting is used with permission-set groups; it does not conditionally hide fields on a page.
• D — Field-Level Security: FLS would remove field visibility at the security level. If fields are hidden by FLS, users generally cannot report on or access those fields, conflicting with the requirement that both users report on all data.

• Microsoft Entra Connect synchronization
• AD FS
• Active Directory Domain Services

• SendGrid with advanced reporting: Used for application email delivery, not directory synchronization monitoring.
• Action group: Used with Azure Monitor alerts, but it is not the native monitoring solution for Microsoft Entra Connect synchronization health.
• Azure Network Watcher: Monitors Azure networking, not identity synchronization.

• Minimum and maximum values
• Number of distinct values
• NULL information
• Other metadata used for pruning

• Help the team identify the root causes of delays.
• Empower the team to improve its workflow and practices.
• Facilitate removal of impediments.
• Avoid directing the team toward a solution without its involvement.
• Protect quality and sustainable delivery rather than simply accelerating everything.

• A: An impediment log may help, but merely recording problems does not empower the team to solve them.
• B: Directing the team to solutions conflicts with self-management.
• C: Adding impediments to the product backlog may incorrectly treat internal obstacles as product features and delays their resolution.

• Warehouse size: Larger warehouses use more credits per unit of time than smaller ones.
• Number of clusters: A multi-cluster warehouse can run multiple clusters, and each active cluster consumes credits. Therefore, increasing the maximum or active cluster count can increase consumption.

• Number of users: More users may cause more workload, but users themselves do not consume credits.
• Amount of data processed: Snowflake warehouses are not charged directly by the amount of data scanned. However, processing more data may cause the warehouse to run longer, indirectly increasing credits.

• The Print Spooler is a Windows service.
• Services can have dependencies—other services that must be running first.
• If a dependency fails, the Print Spooler may repeatedly fail to start.
• In the Services tool, the technician can view the service’s Dependencies tab, start or restart services, and configure startup behavior.

• Processes: Shows currently running applications and processes.
• Startup: Controls which programs launch during Windows startup.
• Performance: Displays resource usage such as CPU, memory, disk, and network activity.

• File policy in Microsoft Defender for Cloud Apps: Can detect activity involving files, but it is not designed specifically to investigate risk from departing or deleted users.
• Access review policy in Microsoft Entra: Reviews whether users should retain access to resources; it does not detect historical document downloads.
• Alert policy in Microsoft Defender for Office 365: Primarily handles alerts for email and collaboration threats, not insider-risk investigations involving departed users.

• Labels control access and protection, not blanket exclusion.
• If the user has permission to open a labeled file—especially if the label allows authenticated users to view it—Copilot can use that file in a summary.
• If the label applies encryption and the user lacks the required usage rights, Copilot should not use the file or reveal its contents.
• Copilot honors the user’s existing permissions, so it should not expose labeled content to an unauthorized user.

• Footprinting is reconnaissance used to map an organization’s network, hosts, naming conventions, and services.
• A name such as fshare.int.complia.org suggests an internal file-sharing host (fshare) and an internal naming structure (int).
• This can reveal useful information to an attacker before attempting exploitation.

• ISP-assigned address space: Usually determined through public registration and DNS data, not an internal hostname.
• DNS sinkhole bypass: Would involve avoiding redirected malicious-domain queries.
• Initial access: DNS reconnaissance alone does not compromise the server.
• Data exfiltration: DNS tunneling typically generates many encoded or unusually long subdomain queries, not simply a meaningful internal hostname.

• Default route: 0.0.0.0/0; used only when no more specific route exists.
• Network route: A route covering the destination, such as 10.10.13.0/24.
• Host route: An exact 10.10.13.10/32 entry in the routing table.
• Floating static route: A backup static route with a higher administrative distance.

• JDBC
• SnowSQL
• Snowflake Web Interface (UI)
• ODBC
• Python connector

• User2 is in Group1, so CA2 applies.
• CA2 targets Office 365.
• CA2 requires MFA OR an app protection policy.
• User2 has no app protection policy, but if User2 successfully completes MFA, the OR condition is satisfied.
• The device being noncompliant does not matter because CA2 does not require device compliance.
• CA1 applies only to Global Administrators. Unless User2 is also a Global Administrator, CA1 does not apply.

• A class/teacher fact should contain one row per Class ID. It can support the count of classes and contain attributes such as Teacher First Name and Period Number.
• An attendance fact should contain one row per attendance event, such as Class ID + student + date. It supports attendance counts by day and monthly averages.

• Teacher First Name ? Teacher fact
• Period Number ? Attendance fact

DAX 
Sales % of Total = 
DIVIDE( 
    [Total Sales], 
    CALCULATE( 
        [Total Sales], 
        ALLSELECTED(Products) 
    ) 
)

DAX 
Total Sales = 
SUM(Sales[SalesAmount])

Why ALLSELECTED is required

• The numerator, [Total Sales], is evaluated for the current product.
• ALLSELECTED(Products) removes the current product’s visual filter when calculating the denominator.
• It preserves filters applied at the report, page, or slicer level.

Why not ALL(Products)?

DAX 
CALCULATE([Total Sales], ALL(Products))

• Static testing examines source code or compiled code without running it. Since the source code is unavailable, this is not the best choice.
• Dynamic testing evaluates the application while it is running. It is commonly used for black-box testing, so it does not require source-code access.
• Penetration testing simulates attacks and can certainly assess a deployed application, but it is broader than simply evaluating the software’s security.
• Vulnerability testing generally looks for known weaknesses and may not thoroughly test application behavior or business logic.

• Review the risk register.
• Check the documented risk response strategy, such as using a backup resource, reallocating work, or adjusting sequencing.
• Implement the planned response promptly.

• B: Moving the task may affect the critical path and should not be done without first evaluating the planned response and impacts.
• C: Excluding a required task would change scope and business requirements without proper analysis or approval.
• D: Updating lessons learned and the risk log may be appropriate later, but it does not address the immediate problem. First, execute the response.

text 
roles/owner

bash 
gcloud projects get-iam-policy PROJECT_ID

yaml 
bindings: 

members:

  - user:admin@example.com 
  role: roles/owner

• Project-wide SSH keys control VM SSH access, not IAM ownership.
• Identity-Aware Proxy permissions apply to IAP-protected applications, not the complete project IAM policy.
• Audit Logs record activity; they do not directly show the current set of role assignments.

• D — Managers focus on keeping costs low in the short term to maximise profits.

• E — Managers are given incentives to meet or undercut budgets.

• F — Managers delegate responsibility simply to reduce their workload.

• 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.

• Install unauthorized or unsupported software
• Access features blocked by the manufacturer or operating system
• Customize system behavior beyond normal settings

• Document feeder: A scratch, dirt, or debris on the feeder glass or rollers can create a line on every scanned image.
• Pickup rollers: Move paper through the printer; they would not normally create a scanner-only line.
• Corona wire: Affects toner charging and would cause defects on printed output.
• Drum assembly: Also affects printed pages, so faxes and computer print jobs would show the line too.

1. Create Workspace2 with Lakehouse2 — F
2. Migrate the Employee table to Lakehouse2 — E
3. Assign the data engineer the Contributor role for Workspace1 — D

Why

• Sharing Lakehouse1 would not provide the required isolation.
• Viewer access would not allow writing to Customer.
• Giving Contributor access to Workspace2 would expose the sensitive table.

• A. Remove rows where Sales[Status] is Canceled

• E. Remove Sales[Canceled Date]

• B: Removing Sales_Date would remove information users need—the date portion.
• C: Changing Delivery_Time to Integer could alter its meaning or precision and is not necessarily safe.
• D: Splitting the date/time column creates additional columns rather than simply removing unnecessary data.

• Maintain head office control: Transfer pricing generally supports decentralisation rather than direct head-office control.
• Establish centralised decision making: This conflicts with divisional autonomy.
• Develop a top-down culture: Transfer pricing is intended to support empowered divisions and goal congruence, not impose purely top-down management.

• 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.

• Customer needs: Primary focus in agile; guides prioritization and decision-making.
• Organization’s needs: Important constraints, but processes should be tailored when they create waste.
• Agile lead/project manager: Their role is to facilitate value delivery, not prioritize their own preferences.

• Economy: Obtaining inputs at the lowest appropriate cost.
• Efficiency: Making the best use of resources, such as staff, money, and equipment.
• Effectiveness: Achieving the intended objectives or outcomes.

• Complex inputs: A queueable job can accept and retain complex data such as Map<Id, Project__c> and List<Account>.
• Callouts: The class should implement both:

apex 
  public class ProjectJob implements Queueable, Database.AllowsCallouts { 
      // execute method 
  }

• Execution confirmation: System.enqueueJob() returns an AsyncApexJob ID. You can use that ID to query job status and confirm whether the job completed successfully.

• @future(callout=true) supports callouts, but future methods have more restrictive parameter types and return no job ID for tracking.
• Database.AllowsCallouts is only an interface that permits callouts; it is not an asynchronous mechanism by itself.
• Schedulable is intended for jobs that run at a scheduled time, not primarily for submitting a long-running asynchronous operation.

• Company documents
• Databases
• Knowledge bases
• Current web or business data

• A: Describes diversity and inclusive design, not grounding.
• B: Describes explainability or model interpretability.
• D: Describes documenting a model’s capabilities and limitations.

• Complex inputs: Queueable jobs can accept objects such as Map<Id, Project__c> and List<Account> through the class constructor.
• Long-running callouts: Implement Database.AllowsCallouts in the Queueable class.
• Confirmation/status: System.enqueueJob() returns an AsyncApexJob ID, which can be used to query job status and determine whether execution completed successfully.

apex 
public class ProjectQueueable 
    implements Queueable, Database.AllowsCallouts { 


    private Map<Id, Project__c> projects; 
    private List<Account> accounts; 


    public ProjectQueueable( 
        Map<Id, Project__c> projects, 
        List<Account> accounts 
    ) { 
        this.projects = projects; 
        this.accounts = accounts; 
    } 


    public void execute(QueueableContext context) { 
        // Perform the callout 
    } 
}

• @future(callout=true) supports callouts, but future methods accept only primitive values or collections of primitives—not complex sObjects or maps of sObjects.
• Database.AllowsCallouts
 Hyderabad, India