Pegasystems PEGACPBA24V1 Exam Actual Questions
Certified Pega Business Architect 24 (Page 6 )

• If the account name includes the parsed search string, show the element; otherwise hide it.
• In CSS, to show an element you can set display to a visible value (commonly 'block' for block-level elements), and to hide you set display to 'none'.

• The ternary should map true to a visible display value and false to 'none'.
• Therefore the placeholder should be replaced with 'block' : 'none' (so the code becomes: accountName.includes(parsedSearchString) ? 'block' : 'none').

• There are several typos in the snippet (e.g., quesrySelectorAll, toLOwerCase, Style.display). In a working version you’d also fix those to document.querySelectorAll, account.innerHTML.toLowerCase(), and account.style.display.

• Correct answer: A — The degradation of a service.

• Why: A service request is a formal request from a user for something that is pre-approved and routine (e.g., provisioning a laptop, replacing a toner cartridge). Those are typical service request actions. The degradation of a service, however, is an incident: it describes a problem affecting service quality or availability and is handled by Incident Management (and possibly Problem Management), not as a standard service request.

• Quick note on the other options:

• Correct answer: A: The ITIL service value system (SVS).

• The SVS explains how all components (governance, the service value chain, practices, guiding principles, information and technology, partners and resources, and continual improvement) work together to enable value creation from demand to outcomes.

• B: The ITIL guiding principles describe aspirational guidance for decision-making, not how all components/activities interact.
• C: The four dimensions of service management explain areas to consider (organizations/people, information/technology, partners/suppliers, value streams/processes) but don’t describe the integrated system itself.
• D: A service relationship defines the relationship between provider and consumer, not the overall system of components and activities creating value.

• The correct AAA mapping (per Cisco objectives) is:

• Why the given options aren’t fully correct:

• Quick takeaway: when you configure AAA, you should conceptually map them as:

• Example commands (to reinforce concepts):

• All authentication events must be processed by PolicyApp. By using two separate topics, you can route sign-in and sign-out events to the same app (via subscriptions pointing to PolicyApp), ensuring both types are processed.
• Sign-outs must be processed as fast as possible. Isolating sign-out events on their own topic/subscription lets you scale and prioritize that path independently from sign-ins, reducing contention and latency.
• Decoupling the flows provides better control and RBAC granularity. You can apply different access controls and scaling policies per topic/subscription if needed.
• A single subscription with a subject filter (e.g., subjectBeginsWith) would still require handling both event types and wouldn’t offer the same isolation and independent scaling benefits as separate topics and subscriptions.

• A private IP address on the virtual network
• A public IP address associated with its IP configuration

• Quick context: In a three-tier network (Access, Distribution, Core), roles are:

• Why A is correct: The Distribution layer runs Layer 2 and Layer 3 technologies. It often handles VLAN access (L2) and can perform inter-VLAN routing or connect to the core (L3). So it makes sense for the distribution layer to support both L2 and L3.

• Why B is correct: The Core layer is designed to maintain continuous connectivity when devices fail. It is built for high availability and redundancy, providing multiple paths so the network remains reachable even if some components fail.

• Why the others are not correct:

• DNS????????????????

• ???????????

• ????????????????

• Answer: C — 192.168.0.0/25 as summary and 192.168.0.0/27 for each floor

• Why:

• B. Enable column profile — This turns on column profiling, which computes statistics like min and max for each column.
• C. Show column profile in details pane — This ensures the per-column profile is visible in the details pane.
• E. Enable details pane — This makes the details pane available so you can view the column profile there.

• A. Show column value distribution may help with distribution but isn’t specifically about min/max.
• D. Show column quality details shows data quality (valid/null counts), not min/max.

• Options:

• Answer: The correct choice is A (800-61r3).

• NIST SP 800-61 Rev. 3 is the dedicated guide for incident handling/response and reflects the latest guidance on the incident response lifecycle (preparation, detection/analysis, containment, eradication, recovery, post-incident activity).
• 800-61r2 is an older revision of the same incident response guide.
• 800-53 covers security and privacy controls, not a specific incident response standard.
• 800-171 focuses on protecting CUI in non-federal systems and networks, not incident response guidance.

• Answer: D

• The strongest security comes from enforcing access at the storage layer. An IAM policy scoped to the Cognito identity prefix restricts each user to their own S3 prefix (folder), so users can only access their own files regardless of client or server code.
• This per-user isolation reduces risk of cross-user data access and is more robust than UI validation or Lambda/API validation alone.
• Implementation note: attach a policy to the Cognito identity role that allows actions on arn:aws:s3:::your-bucket/${cognito-identity.amazonaws.com:sub}/* (per-user prefix). Ensure TLS in transit and enable at-rest encryption (SSE-S3 or SSE-KMS). Use multipart upload for large files up to 300 MB.

• Transact-SQL (T-SQL) is used to query relational data in Azure SQL Database, not telemetry data from monitoring services.
• To analyze monitoring data from Azure SQL Database Intelligent Insights and Azure Application Insights, you should use the Kusto Query Language (KQL) in Azure Monitor Logs/Log Analytics (and in Application Insights Analytics).
• Using KQL lets you query telemetry tables such as requests, dependencies, pageViews, and customEvents (from App Insights) and any integrated monitoring data you’ve ingested into Log Analytics.

• Ensure Intelligent Insights and Application Insights data is available in a Log Analytics workspace or accessible via Application Insights Analytics.
• Go to Azure Monitor > Logs (or Application Insights > Analytics) and write KQL queries, e.g.:

• The question asks why some tasks appear locked in the HR Guided Setup Module’s Task view.
• The options are:

• C) They require other tasks to be completed first. In guided setup flows, tasks are usually gated by prerequisites to ensure proper sequencing and data/configuration dependencies. You typically unlock a task only after the necessary preceding tasks are finished.

• A) Elevated roles can restrict access in some contexts, but guided setup tasks are commonly gated by prerequisites rather than solely by role.
• B) Deprecation isn’t the general pattern for “locked” tasks in the guided setup.
• D) A plugin activation could unlock certain features, but the common gating mechanism is task dependencies, not plugin state.

• The page shows the answer as D, but based on how HR Guided Setup usually works, the more accurate reason is typically C (prerequisites). If you’re studying, treat C as the conceptual answer and be aware the listed key may be incorrect. If you want, I can walk through each option in more detail.

• A) You can only apply a single template BOM to a service object.

• C) You can modify or delete lines in a BOM template regardless of whether the template has been associated to a service object, or not.

• B) You can apply many template BOMs to a service object — false; typically only one template per service object.
• D) You can modify/delete lines only if not associated — false; you can modify templates even after association (per C).

• prompt: the input or instruction given to the model
• completion: the desired response

json 
{"prompt":"Summarize this customer complaint.","completion":"The customer reports a delayed shipment."}

• B: A .txt file containing CSV-style lines is not automatically a valid fine-tuning dataset. The required structure and format must match the selected Bedrock model.
• C: Provisioned Throughput provides dedicated inference capacity; it does not fine-tune a model.
• D: Journals and textbooks might support domain adaptation or pretraining, but they do not provide the prompt-to-answer examples typically required for supervised fine-tuning.

• Answer: No

• Salesforce search results are filtered by the current user's permissions and sharing rules. This is part of the security model at the record level.
• If two users have different profiles, permission sets, or sharing access, they may see different records in the results for the same keyword.
• If both users have identical access, their results should be the same; differences arise from differences in visibility rather than the search itself.

• You want: a row for each year and each product (year+product), plus a summary row for each year that totals all products (year only).
• GROUP BY ROLLUP(YEAR(SO.ModifiedDate), P.Name) yields:

• GROUP BY CUBE(YEAR(SO.ModifiedDate), P.Name) produces all combinations of the grouping columns, including:

• This adds extra rows (per-year totals by product across all years and a grand total) that aren’t needed for your stated goal.

• If you want exactly the (Year, Product) and (Year) rows, you can use GROUPING SETS ((Year, Product), (Year)) which is equivalent to Rollup in this two-column case but makes intent explicit.

• SELECT YEAR(SO.ModifiedDate) AS OrderYear, P.Name AS ProductName, SUM(SO.OrderQty) AS TotalQty

• The diagnostic output shows that the protocol is TCP (proto=6) and the session state is 2.
• In FortiGate’s session output, state=2 maps to SYN_SENT. This means the TCP SYN has been sent but the handshake hasn’t completed yet.
• Therefore, the session is not ESTABLISHED, FIN/ACK-related states, or other states; it’s in SYN_SENT.

• Server — provides services or resources
• Endpoint — a user device connected to the network
• Ethernet — a networking technology, not a filtering device
• Firewall — filters and controls traffic

• Users retain their existing usernames and passwords.
• Existing accounts can be used to access Azure-based resources.
• Administrators avoid manually recreating thousands of accounts.
• The transition is less disruptive before the on-premises data center is retired.

• The requirement: SQL authentication cannot be used for any databases on Server1, and the solution must be enforced centrally at the server level.
• Correct choice (C): Enable Microsoft Entra-only authentication for Server1.

• Why not the others:

Why B works

• AWS KMS keys are Regional resources. A normal customer managed key in Region A cannot be used directly in Region B.
• A customer managed multi-Region KMS key (MRK) has related key replicas in both Regions. The replicas share key material and key ID, although each has a Regional ARN.
• With client-side encryption, the application encrypts the data before storing it in S3. Cross-Region replication then copies already-encrypted objects, so S3 does not need to decrypt and re-encrypt them with a different Regional key.

Why the other choices are weaker

• A and C: SSE-S3 uses Amazon-managed S3 keys, not the required customer managed KMS key.
• D: SSE-KMS can work only if the solution creates and configures the appropriate KMS key or multi-Region key replica in each Region. As written, it says to create a customer managed KMS key in each Region, which implies separate keys—not the same KMS key. Replication also requires additional KMS permissions and destination encryption configuration.

• The question asks which Azure support plans allow you to open new support requests.

• Key concept:

• Therefore, the correct choice is the plan(s) other than Basic (i.e., Developer, Standard, Professional Direct, Premier). If the provided key lists only one option as correct (A), it may be incomplete or misleading—the official plans page shows that Basic does not meet the requirement, while the paid plans do. See: https://azure.microsoft.com/en-us/support/plans/

• In ServiceNow, each customer typically gets their own instance (prod, dev, test). This means the architecture is multi-instance, not a single instance.
• A single-instance, multi-tenant setup would be one shared instance serving many tenants. ServiceNow uses separate instances per customer (data and configuration isolated per tenant), so it is not a single-instance, multi-tenant architecture.
• In practice: you access a customer’s instance like customerA.service-now.com; other customers have their own distinct instances. The platform code is shared, but the data/configuration are isolated per instance.

1. Download the updated VPN client configuration package from the Azure VPN gateway.
2. Remove or update the existing VPN client configuration on the Windows 10 workstation.
3. Install the new package and reconnect.

• On-Demand: You pay by the hour with no long-term commitment. This is ideal for workloads that are infrequent or have highly variable usage. Since this job runs only 24 hours once per year, you pay only for those 24 hours, with no wasted upfront or long-term payments.
• Reserved Instances: Require a 1- or 3-year commitment and pay for capacity whether you use it or not. For a workload that runs just 24 hours a year, you’d be paying for most of the term unused, making it far less cost-efficient.
• Spot Instances: Can be interrupted whenever AWS needs capacity, which is unacceptable for an uninterruptible workload.
• Dedicated Instances: Generally more expensive and aimed at licensing or compliance requirements; not needed for this use case.

• The 99.99% availability SLA for VMs is achieved when you run VMs across two or more Availability Zones.
• Two VMs in a single Availability Zone do not meet the 99.99% target (their SLA is lower, e.g., around 99.95% or less depending on configuration).

• Deploy at least two VMs across two different Availability Zones (one VM in each zone, or both in two zones with a load balancer).
• This provides the required zone redundancy and the 99.99% SLA.

• Goal: Guests should not use cameras, but company users can.
• Correct configuration: Guest access settings in the Org-wide settings.

• External access: Controls external-domain communication, not guest capabilities inside Teams.
• Teams settings in Org-wide settings: Too generic; doesn’t specifically target guest capabilities.
• Audio & Video in the default Meeting Policy: Would affect everyone assigned to that policy. To meet the requirement without impacting internal users, you’d need separate policies or guest-specific settings; the exam focuses on the guest-access policy.

• An IDS monitors network traffic for signs of attacks and raises alerts. It can be deployed out-of-band (via a SPAN/mirror port or a tap) so it analyzes traffic without being inline, meaning it doesn’t measurably affect latency.
• An IPS (intrusion prevention system) is inline and can block threats, but that processing can introduce some latency and potential throughput impact.
• A firewall also inspects traffic and can add latency, though usually modest with proper hardware, but its primary purpose isn’t continuous passive analysis.
• A load balancer distributes traffic and isn’t used for intrusion analysis.

• The Scrum Guide specifies four required events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. These events enable transparency, inspection, and adaptation.
• The other items listed are not mandatory under Scrum:

• UPS (uninterruptible power supply) provides battery backup (time to save work and shut down).
• Surge protector only blocks surges; it does not provide backup power.
• To maximize uptime for essential tasks, put the devices that must stay powered during an outage on the UPS. Put less-critical devices on the surge protector or a wall outlet.

• Put on the UPS: the desktop computer, monitor, network gear (router/modem), and any external drives or essential peripherals you need to keep running to save to the cloud.
• Put on the surge protector (or wall outlet): nonessential devices like printers, scanners, speakers, or lamps.

• A — SCIM synchronizes changes to user attributes from the identity provider to GitHub.
• B — SCIM deactivates GitHub accounts when users are removed or deactivated in the identity provider.
• D — SCIM automates user provisioning when new users are added to the identity provider.

• C: SCIM does not delete organization repositories.
• E: SCIM does not generate REST API authentication tokens.
• F: SCIM handles identity lifecycle management, not repository permission configuration based on roles.

• Box 1: Azure Lighthouse — ??? ??????? ? ?????????? ????????? ? ?????????? Entra tenants. ??? ??????????? ??? ??? ????? ????? ? VM ? ?????? ?????????/????????.
• Box 2: Azure Monitor Agent ? ?????????????? Data Collection Rules (DCR) — AMA ???????? ??????? Windows (????????, Security Logs) ? DCR ??????????, ????? ??????? ???????? ? ???? ?????????? (? ?????? Log Analytics workspace).

• Storage accounts: storage1, storage2, and storage3
• Log Analytics workspace: Analytics3

• Azure Backup reports can send the AzureBackupReports diagnostic log to eligible storage accounts. The storage account’s subscription and region do not have to match the Recovery Services vault, so all three listed storage accounts are valid.
• The Log Analytics workspace must be in the same region as the Recovery Services vault for this configuration. Vault1 and Analytics3 are both in West Europe, making Analytics3 the valid workspace.

• What the goal is: You want to add guest (external) users to your Azure AD tenant contoso.com, one entry per external user in a CSV.

• The proposed solution uses New-AzureADUser for each external user. Why this isn’t correct: New-AzureADUser creates a regular (internal) user in your directory. It does not create a guest/B2B user invite. So you’d end up with 500 ordinary accounts, not guest accounts with external access.

• The correct approach: Use New-AzureADMSInvitation for each external user. This invites the external user to your directory and creates a guest user (a B2B collaboration user) in your tenant. The invited user then accepts the invitation and gains access as a guest.

• Azure AD vs directory/tenant: Azure AD is the cloud identity service. A directory (also called a tenant) is your specific instance of that service (contoso.com in your scenario). The terms are often used interchangeably in exams.
• Guest user vs internal user: A guest user is external to your organization; an internal user is created directly in your directory as a normal employee/user account.
• B2B invitation: The process of inviting external users so they can collaborate in your resources; New-AzureADMSInvitation is designed for this.

• Increase/decrease the number of epochs: Changes how long training runs, but does not reuse a pre-trained model.
• Unsupervised learning: Trains from unlabeled data and does not specifically address adapting an existing model.

• Event | search "error"
• Event | where EventType == "error"
• search in (Event) "error"

• Startup scripts run at computer startup, before any user logs on, making them ideal for machine-wide configuration on each new VM.
• They execute under the Local System account, which is appropriate for initial setup tasks.
• Linking a GPO to the OU ensures every new VM in that domain automatically receives the configuration—great for scalability.

• A) SetupComplete.cmd runs only once, right after Windows Setup, not on every boot, so it isn’t ideal for provisioning multiple VMs consistently.
• B) Logon scripts run per user, not per machine, so they aren’t reliable for initial VM configuration before a user signs in.
• D) Placing scripts in a VHD doesn’t automatically execute them.

• A) macOS with PowerShell Core 6.0 installed — not enough by itself (Az module must be installed as well). So not guaranteed.
• B) Windows 10 with the Azure PowerShell module installed — yes. PowerShell on Windows with Az loaded can run the script.
• C) Linux with the Azure PowerShell module installed — yes. PowerShell Core on Linux with Az can run the script.
• D) Linux with Azure CLI tools installed — no. The script is PowerShell-based (Az), not Azure CLI.
• E) Chrome OS with Azure Cloud Shell — yes. Cloud Shell provides an environment with Az available and can run PowerShell in the browser.

• As the project progresses, you gain information, refine requirements, and lock down baselines (scope, schedule, cost). This reduces overall risk and uncertainty because more is known and addressed.
• At the same time, changes become more costly over time. Later changes can affect already approved baselines, cause rework, impact the critical path, require more coordination, and incur penalties or delays, all of which raise the cost of making changes.

• Permanent table (E): Correct. A dropped permanent table can be restored with UNDROP TABLE during its Time Travel retention period. Permanent tables also have Fail-safe protection.
• Transient table: It can also generally be restored during its shorter Time Travel period, although it has no Fail-safe. Therefore, excluding it makes the question questionable.
• Temporary table: Usually cannot be recovered after it is dropped; its lifecycle is limited to the session.
• Materialized view (D): The answer key treats it as recoverable, but recovery behavior depends on the specific Snowflake object/version capabilities. It should not be confused with an ordinary view.

• Answer: A) Clear the Windows event logs

• Windows event logs (System, Security, Application) are key forensic artifacts. If an attacker clears these logs, there’s no built-in local record of actions taken, making it harder for investigators to trace what happened.

• Modify the system time: may misalign timestamps but does not erase past events and can be easily detected.
• Alter log permissions: could prevent new log entries, but it doesn’t remove existing ones and can raise alarms due to permission changes.
• Reduce log retention settings: affects only future logs; it doesn’t wipe already recorded activity.

• In real environments, defenders mitigate this risk with tamper-evident, centralized logging (remote SIEM, write-once storage, log integrity checks) to preserve evidence even if a host is compromised.

• 345 Patch management: 3.0 - Implementation
• 346 Obfuscation: 2.0 - Architecture and Design
• 347 Host isolation: 4.0 - Operations and Incident Response
• 348 IoT unencrypted traffic: 1.0 - Threats, Attacks and Vulnerabilities
• 349 Tabletop exercise: 4.0 - Operations and Incident Response
• 350 CVSS: 1.0 - Threats, Attacks and Vulnerabilities
• 351 Conflict of interest: 5.0 - Governance, Risk and Compliance
• 352 Fail-open (availability focus): 4.0 - Operations and Incident Response (can vary by version)

• Correct choice: Box 1 = Yes, Box 2 = Yes, Box 3 = No (Answer: A)

• Box 1: Yes – Microsoft Purview Compliance Manager provides a risk-based compliance score that helps you understand your overall compliance posture. The score reflects how well you’re meeting regulatory requirements and internal policies.
• Box 2: Yes – It also offers step-by-step remediation guidance through actionable “improvement actions.” These guide you to implement fixes and align controls, often with links to the relevant consoles.
• Box 3: No – Compliance Manager is not part of Microsoft Defender. It is part of Microsoft Purview. Defender is a separate security product family, while Compliance Manager is in Purview for compliance risk and remediation.

• Use Purview Compliance Manager to view your compliance score and follow improvement actions.
• Improvement actions provide actionable steps and guidance for remediation.
• Defender and Purview are distinct services; do not confuse their scopes.

• Pay-as-you-go in Azure is an operating expense (OPEX) model, not an “elastic” expenditure model.
• Elastic or scalable terms describe capacity planning, not the cost category. The cost should be treated as OPEX since you pay for usage each month.
• The parallel question (Question 12) shows the correct approach is using an operational expenditure model.

• L2TP uses UDP port 1701 for the L2TP control channel.
• The destination port is 1701; the source port is a dynamically chosen ephemeral port on the client (not 1701).
• Therefore the statement that both source and destination ports are 1710 is incorrect (and 1710 is not the standard L2TP port).

• The destination port should be 1701, not 1710.
• The source port should be an ephemeral port chosen by the client, not 1701.

• To use a custom foundation model (CFM) with Amazon Bedrock, you must register the model with the SageMaker Model Registry. This provides versioning, governance, and a concrete reference that Bedrock can load and invoke.

• “Purchase Provisioned Throughput” is not a concept used for Bedrock/custom models.
• Bedrock handles the model hosting and scaling; you don’t need to buy provisioned throughput for the custom model.

• After registering the model, you’ll need to grant Bedrock access to the model (D) so Bedrock can execute it. However, the essential initial step that makes the custom model usable in Bedrock is C.