IIBA CCBA Exam Prep
Certification of Competency in Business Analysis (Page 45 )

• To mitigate resistance, the BA should directly engage the stakeholders who are pushing back (the technical team) to uncover their concerns, constraints, and reasons for resisting the end-of-project handover.
• This enables collaborative problem-solving and may lead to adjustments (e.g., intermediate deliverables, phased rollouts, or alignment of acceptance criteria) that satisfy both business and technical needs.
• Escalating to the sponsor or emailing the business team may not address the root causes of resistance. Reassessing objectives could be useful later, but the immediate best practice is to have a targeted discussion with the technical team to understand and resolve concerns.

• Job shadowing is an elicitation technique that is part of the broader job observation approach. The observer watches workers perform tasks (either passively or actively) to understand the workflow, especially when the worker cannot articulate the process themselves.
• The other options are not elicitation techniques tied to job observation: A) Identifying stakeholders is an initial BA activity; C) Defining and determining business analysis processes is part of planning; D) Planning how requirements will be approached, traced, and prioritized is elicitation planning (a precursor to elicitation), not the observation-based elicitation.

• There are two solutions: A is worth $456,000 to the organization, B is worth $565,000.
• Management chooses A due to lower cost, less risk, and faster completion.
• The opportunity cost is the value of the best alternative that was not chosen. Since B has the higher value ($565,000) and wasn’t chosen, the foregone value is $565,000.
• Note: The \(|565k - 456k| = 109k\) is the difference in value, not the opportunity cost.

• Microsoft Teams: Connects to Teams-related data, but it isn’t the primary connector for the Power Apps data tables.
• Personal Analytics: Provides personal productivity insights, not application data.
• SQL Server database: Only applies if the app explicitly uses SQL Server as its data source.
• Dataflows: Used for preparing and centralizing data, not as the normal direct connection to a Power Apps app.

• A is correct: Days beyond the included period incur an extra daily charge.
• D is incorrect: Daily use after 10 days is not free.
• B and C: Data-transfer pricing can depend on the direction and service terms. The exam’s intended distinction is that the included device usage period is the clearly stated no-cost benefit.

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

• AWS Audit Manager continuously collects evidence from AWS services and helps assess whether workloads comply with regulatory frameworks and internal policies. It can produce audit-ready reports.
• AWS Config records resource configurations and evaluates them against compliance rules. For example, it can check whether encryption, logging, or access settings meet company requirements.

• Amazon Inspector identifies software vulnerabilities and unintended network exposure, not general policy or regulatory compliance.
• Amazon CloudWatch monitors metrics, logs, and operational events, but is not primarily a compliance assessment service.
• AWS CloudTrail records API activity for auditing and investigation. It supports compliance, but does not itself provide the structured compliance assessment capabilities of Audit Manager and Config.

• Ablauf: Er wird in der gleichen Transaktion ausgeführt, bei der z. B. ein Datensatz erstellt oder aktualisiert wird. Der Benutzer wartet, bis der Workflow abgeschlossen ist.
• Stufen: Kann vor dem Vorgang (pre-operation) oder nach dem Vorgang (post-operation) laufen.
• Zweck: Sofortige Validierung oder Anpassung von Daten, ggf. auch das Verhindern eines Vorgangs, wenn Bedingungen nicht erfüllt sind.

• Automatisierte Flows (Power Automate, automatisierte/ Background Flows) laufen asynchron im Hintergrund, nachdem der Trigger erkannt wurde, und blockieren den Benutzer nicht.

• B — Single customer login across properties: Customer 360 Identity provides centralized identity services, allowing an organization to recognize a customer across multiple digital properties and applications. This helps UC understand authenticated activity as part of a broader customer identity.

• C — Multi-brand support: Customer 360 Identity can support multiple brands and user experiences. Identity services can remain centralized while correlating a customer’s activity across different corporate brands or channels.

• A: Customer 360 Identity does not automatically populate all data into Customer 360 Data Manager and Customer 360 Audiences. Integration and data configuration are still required.
• D: Tracking anonymous activity and linking it after sign-up may be possible through broader customer-data and tracking implementations, but it is not the primary Customer 360 Identity benefit tested here. Identity focuses mainly on authentication, registration, and cross-property identity correlation.

• Actual filename: Document.xml.txt
• Explorer displays: Document.xml
• File type: Text Document (.txt)

text 
Document.txt ? Document.xml

• If the Facebook user is new, Salesforce invokes createUser.
• If the user already exists, Salesforce can invoke updateUser.
• The handler can read the latest data from Facebook, such as name, email, or other profile attributes, and update the corresponding Salesforce user.

• B: A scheduled job is unnecessary and would not provide real-time synchronization during authentication.
• C: A Facebook signed request is not the standard mechanism for updating Salesforce user records in this authentication-provider setup.
• D: SAML Just-in-Time provisioning applies to SAML identity providers, not Facebook OAuth authentication.

• Correct choices: A and D.

• Why not B, C, or E?

• Hardware and infrastructure
• System software
• Networks and communications
• Technology platforms and services

• Business Architecture: Defines business strategy, organization, functions, and processes.
• Data Architecture: Defines the structure and management of enterprise data.
• Application Architecture: Describes application systems and how they interact to support business and data processing.

• vSmart controls the overlay control plane. It uses OMP to exchange routing information, distribute policies, and determine how WAN Edge devices reach one another.
• vManage is the centralized management and configuration platform.
• vBond is the orchestrator. It helps devices authenticate, discover controllers, and traverse NAT during onboarding.
• APIC-EM is not the SD-WAN control-plane component described here.

• User1 can sign in because the account is cloud-only. It does not depend on the on-premises domain.
• User3 can sign in because the account uses Password Hash Synchronization (PHS). Azure AD has a synchronized password hash and can validate the sign-in even when connectivity to on-premises Active Directory is unavailable.
• User2 cannot sign in because the account relies on Pass-through Authentication (PTA). PTA sends the authentication request to an on-premises PTA agent, which must contact a domain controller. With the internet connection from on-premises lost, that validation cannot occur.

• 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

Flat organisation

• Few levels of management
• A wide span of control—managers supervise many employees
• Shorter communication channels
• More employee autonomy and quicker decisions
• Fewer formal promotion levels

Tall organisation

• Many levels of management
• A narrow span of control—managers supervise relatively few employees
• A clear hierarchy and reporting structure
• More formal supervision and communication channels
• More obvious promotion and career stages

• Customers access the portal without needing a full Dynamics 365 license.
• They submit case information through portal forms.
• The submitted data is stored in Dataverse tables, such as the Case table.
• Security is controlled using web roles and table permissions, so customers can access only appropriate records.

• Dynamics 365 Connector — connects apps to Dynamics 365 data but is not the portal’s underlying data platform.
• Microsoft SharePoint — useful for documents and collaboration, not the standard case-management data source for portals.
• Microsoft Azure Storage — stores files or other data, but is not the native portal business-data platform.

• Control plane: Managed by Databricks and contains the Databricks web application, workspace services, cluster management, and job orchestration.
• Data plane: Runs in your cloud account and contains compute resources such as:

• Worker node: Data plane compute.
• Driver node: Data plane compute.
• JDBC data source: Usually an external data system.
• Databricks Filesystem (DBFS): Provides storage access and is backed by cloud object storage rather than being entirely part of the control plane.

• Aggregation happens once, during the scheduled job.
• Dashboard users query a relatively small, precomputed table.
• Repeated users do not trigger expensive aggregations against the detailed sales table.
• Overwriting is appropriate because the summary is rebuilt for the reporting period.

• B: Structured Streaming is unnecessary for data that only needs daily refreshes and adds operational/compute overhead.
• C: A view recomputes the aggregation at query time, increasing latency and query cost.
• D: Delta caching may improve reads but does not replace the need to materialize the expensive aggregation, and cache availability is not the main design guarantee.

• GPU: A failure may cause no video output, but the PC usually still powers on.
• RAM: Can prevent booting or produce error beeps, but fans and power indicators generally work.
• CPU: Can prevent startup or booting, but it usually does not cause a completely lifeless system.

• The listener has a virtual IP address on the load balancer.
• The active SQL Server replica must respond using the listener’s IP address, not its own VM IP.
• Floating IP allows the listener IP to be preserved and returned by the active replica.
• This is required for the SQL Always On listener configuration.

• A health probe for the SQL listener/cluster role
• The SQL Server listener port, commonly 1433
• Appropriate backend pool membership

• tag=Priv searches the tag field for values beginning with Priv. The wildcard can match the remaining characters, so it matches Privileged.
• tag=Priv would search for the exact tag Priv, not Privileged.
• tag=priv* uses lowercase priv; tag matching is treated as case-sensitive here, so it may not match the tag Privileged.
• tag=privileged uses the wrong capitalization for the exact tag.

• Amazon DynamoDB — Managed NoSQL database, not PostgreSQL.
• Amazon Athena — Serverless service for querying data in S3; intended for analytics, not OLTP.
• Amazon EMR — Managed cluster platform for big-data frameworks such as Hadoop and Spark.

• Sending calls to available agents quickly
• Balancing interactions across agents
• Preventing calls from being handled manually one at a time

• Workforce Management: Forecasts demand and schedules enough staff; it supports wait-time reduction but does not directly distribute calls.
• Skill-based Routing: Routes calls based on agent skills and may improve the customer experience, but the question is asking about the core feature that distributes calls efficiently.
• IVR: Lets callers navigate menus and self-service options; it does not primarily assign calls to agents.

• A: Security groups do not control traffic to an S3 gateway endpoint in this way. Gateway endpoints are configured through route tables.
• B: An S3 bucket policy may be needed for authorization, but the error specifically indicates a connectivity or endpoint-routing problem.
• C: Glue connection settings do not require a fully qualified domain name to resolve this endpoint issue.

• Create and manage catalogs of approved IT services
• Govern and publish infrastructure-as-code (IaC) templates, commonly AWS CloudFormation templates
• Control which users can deploy specific products and configurations
• Apply versioning, permissions, and deployment constraints

• AWS Resource Explorer: Searches and discovers AWS resources; it does not govern IaC templates.
• AWS Organizations: Manages multiple AWS accounts, policies, and consolidated billing.
• AWS Systems Manager: Helps operate and manage deployed resources, such as patching and automation, but is not primarily a catalog for governed IaC products.

• Forecasting lets sales leaders predict revenue for upcoming fiscal periods, compare forecasts with targets, and review performance by salesperson or team.
• Opportunity Stages help determine the likelihood that opportunities will close. Each stage can have a probability, which contributes to forecast calculations.

• Sales Quotes: Used to present pricing or product proposals to customers; they do not provide revenue forecasting.
• Opportunity List View: Helps users filter and view opportunities, but it is not the forecasting tool.

• Self-signed certificate: Causes a certificate warning, not incorrect IP resolution.
• Nameserver record: A DNS record problem would typically affect multiple users, not just one.
• IP helper: Relays DHCP or other broadcast traffic between networks; it does not control website name resolution.

• The policy is confidential, and the requester is no longer authorized merely because they used to work for the organization.
• The security professional should not disclose it by email or display it on a device without authorization.
• Using official channels allows the organization’s owner or information custodian to verify:

• A) configure matching hold and delay timers

• B) configure matching key-strings

• C) configure matching priority values

• D) configure unique virtual IP addresses

• Conserve public IPv4 addresses: IPv4 addresses are limited, so many internal devices share a smaller number of public addresses through NAT.
• Reduce direct exposure: Private addresses are not directly routable from the public Internet, which helps reduce unsolicited access to internal devices.

• Compensating control: The server is end-of-life, so it may no longer receive security patches or support. Placing it on a restricted VLAN provides an alternative layer of protection by reducing who can access it and limiting its exposure.
• Technical control: VLAN segmentation and access control lists (ACLs) are technology-based mechanisms that enforce network access restrictions automatically.

• Managerial: Policies, procedures, and governance—not network configuration.
• Physical: Locks, guards, or barriers.
• Corrective: Restores systems after an incident.
• Detective: Identifies suspicious activity rather than restricting access.
• Deterrent: Discourages behavior but does not enforce access rules.

1. The sender hashes the original message and sends the message plus its hash.
2. The receiver applies the same hashing algorithm to the received message.
3. The receiver compares the newly calculated hash with the sender’s hash.
4. Matching values indicate that the message was not altered in transit.

• A binary image is not the normal description of a hash result.
• Using a different algorithm produces a different type of digest, so the values cannot be directly compared.
• Hashing verifies integrity, but by itself does not prove who sent the message. Digital signatures or MACs address authentication and integrity together.

• Basic: Self-help only; no technical support or design assessment.
• Standard: Technical support, but not the full proactive architectural guidance required here.
• Professional Direct: Provides proactive guidance and architecture-related assistance.
• Premier: Also supports this, but is a more expensive, enterprise-level option.

kusto 
Event | where EventType == "error"

• == is the KQL equality operator.
• -eq is a PowerShell operator, not KQL.
• is is not the correct equality operator in this context.

text 
Event | where EventType –eq "error"

• Event | search "error" — valid, broad search.
• search in (Event) "error" — valid, broad search.
• Event | where EventType == "error" — valid, targeted filter.

• Idioma: “Responda em português.”
• Tamanho: “Responda em até três frases.”
• Formato: “Use uma lista com três recomendações.”
• Objetivo: “Recomende produtos com base nas necessidades do cliente.”

• Mudar o tamanho do LLM: pode alterar capacidade e custo, mas não garante idioma ou respostas curtas.
• Aumentar a temperatura: aumenta a criatividade e a aleatoriedade; não controla diretamente o tamanho ou idioma.
• Aumentar o Top K: permite considerar mais tokens prováveis, aumentando a variedade; também não é o mecanismo principal para controlar idioma ou comprimento.

• Admin access to the deployment pipeline (B) – lets the developers use the pipeline and deploy content.
• Contributor access to the Development and Test workspaces (E) – required to deploy items into those workspaces.
• Viewer access to the Production workspace (D) – lets them view Production content without allowing deployment or modification.

• Contributor access to Production (F), because that could allow changes or deployment there.
• Viewer access to Development/Test (C), because Viewer is insufficient for deployment.
• Build permission to Production semantic models (A), because building reports on a semantic model is not required merely to view Production items.

• The requirement explicitly says the organization wants to use SAML to secure Salesforce API access.
• The SAML Bearer Assertion Flow exchanges a SAML assertion for a Salesforce OAuth access token.
• It is intended for server-to-server or other noninteractive integrations where the application has already been authenticated by an identity provider.
• The connected app can be configured so administrators authorize or preauthorize applications that consume the APIs.

• B — JWT Bearer Flow: Uses a signed JWT, not a SAML assertion. It would be appropriate if the requirement specified JWT-based authentication.
• C — SAML Assertion Flow: This is not the standard Salesforce OAuth flow name; the relevant name is OAuth 2.0 SAML Bearer Assertion Flow.
• D — User-Agent Flow: Designed for interactive browser-based authorization, not a SAML-based server-to-server integration.

• A. Implement retries with exponential backoff

• C. Reduce the frequency and/or size of requests

• B. Use PutRecord instead of PutRecords — PutRecord sends one record per call and does not remove the underlying throughput limitation. It may increase request overhead.
• D. Use Amazon SNS instead — SNS is not a direct fix for Kinesis shard throttling and changes the required streaming architecture.
• E. Reduce KCL consumers — KCL consumers read from Kinesis; they do not solve producer-side PutRecords throttling.

• A: Using an external OAuth 2.0 identity provider could provide unified identity, but it does not specifically address Salesforce capacity or high-volume login limits.
• B: Making the Experience Cloud community a SAML identity provider and using JIT provisioning is a possible federation pattern, but it may not be appropriate for this scale without Salesforce validation.
• C: A default account is unrelated to solving identity unification and high login throughput. Person Accounts can be supported in appropriate B2C Commerce integrations.

json 
{ 
  "Effect": "Deny", 
  "NotAction": [ 
    "iam:*", 
    "route53:*", 
    "cloudfront:*", 
    "support:*" 
  ], 
  "Resource": "*", 
  "Condition": { 
    "StringNotEquals": { 
      "aws:RequestedRegion": "eu-west-1" 
    } 
  } 
}

• SCPs set maximum permissions; they do not grant permissions. The default SCP allows actions, so the restriction must be an explicit Deny.
• aws:RequestedRegion checks the Region targeted by an API request.
• StringNotEquals: eu-west-1 denies requests directed to every other Region.
• NotAction allows designated global services to remain usable because they do not operate in a single AWS Region.
• Attaching the SCP to the OU makes it apply to existing accounts and accounts later added to that OU.

• Correct answer: B (No, it does not).

• A purchase agreement in Dynamics 365 SCM is a vendor-side price arrangement. It sets prices/discounts for what your company buys from suppliers, not for what you sell to customers.
• The objective in Question 2 is to give clients a quantity-based discount on items they purchase from you. To accomplish this, you should configure a sales price / trade agreement (on the customer/sales side), not a purchase agreement.
• In a sales price trade agreement, you can define quantity breaks such as:

• Create a Sales price trade agreement for the item and relevant customer (or customer group).
• Add quantity breaks: 51–100 with 10% discount, 101+ with 15% discount.
• Ensure the agreement is active for the desired date range.

• The files are stored in a document library, which is exposed through the SharePoint Folder connector.
• The connector returns file metadata, including Folder Path, Name, and Content.
• In Power Query, filter Folder Path so only files in the manufacturing reports folder are retained.
• You can then combine the remaining Excel files because they all have the same structure.

• SharePoint List is for SharePoint lists, not document-library files.
• Combine & Load combines files immediately, before you filter to the required folder, and may include unwanted files.
• Transform gives you the opportunity to filter the file list first, which is more efficient and targeted.

sql 
SELECT COUNT(*) FROM table;

• A: It does not normally need to scan all data files for this operation.
• B: Results are not simply reused from a query cache every time. Caching is separate from Delta’s metadata optimization.
• D: The relevant metadata is maintained through the Delta transaction log, not directly treated as a Parquet-file metadata operation in this context.

• S3 Lifecycle rules automate actions such as transitioning objects to different storage classes or deleting old objects.
• S3 bucket policies control access permissions; they do not preserve earlier object versions.
• S3 server-side encryption protects data confidentiality by encrypting objects at rest, but it does not prevent deletion or overwriting.

• Accidental deletion or overwriting ? S3 Versioning
• Unauthorized access ? bucket policies and IAM
• Data encryption ? server-side encryption

• Strongest encryption algorithms: Choose the strongest available encryption and integrity options, typically AES with the largest key size and a secure integrity algorithm.
• Encrypt all traffic: Select tunnel mode rather than transport mode. Tunnel mode encrypts the entire original IP packet, which is appropriate for a site-to-site VPN between branch networks.
• Secret-password authentication: Configure a pre-shared key (PSK) on both VPN concentrators. The key must match at both ends.

• Issuer: Identifies the party issuing a SAML message, commonly the IdP in the SAML assertion. It is not the Salesforce setting used to distinguish Salesforce from other service providers.
• Identity Provider Login URL: Specifies where Salesforce sends users for authentication; it does not identify Salesforce.
• SAML Identity Location: Specifies where the user identity is found in the SAML assertion, such as the subject or an attribute.