GARP ICBRR Exam Prep
International Certificate in Banking Risk and Regulation (ICBRR) (Page 30 )

• Create and manage approved IT services as products
• Control which users can deploy those products
• Apply governance, permissions, and constraints
• Use and manage infrastructure-as-code templates, such as AWS CloudFormation templates

• AWS Resource Explorer: Helps find and browse AWS resources; it does not govern IaC deployments.
• AWS Organizations: Manages accounts, consolidated billing, and organization-wide policies.
• AWS Systems Manager: Provides operational management, such as patching, automation, and parameter storage, but it is not primarily used to catalog and govern IaC-based service deployments.

• A — Can help keep costs down and improve quality: The provider may have specialist expertise, efficient systems and economies of scale.
• B — There is a known fee if agreed in advance: A fixed or agreed fee can make costs more predictable and support budgeting.
• C — Allows management to focus on core operations and issues: Senior managers spend less time supervising routine finance processes and more time on strategic matters.

• Increased control: Control may decrease because the activity is performed externally.
• Increased independence: The organisation becomes dependent on the supplier.
• Increased understanding of the outsourcing business: The internal organisation usually has greater business knowledge; the provider may initially lack it.
• Increased confidentiality: Sharing financial information externally may create confidentiality risks.
• Internal expertise improved: Outsourcing can reduce opportunities to develop internal finance skills.

• SQL injection (SQLi): Attacks databases by inserting malicious SQL commands.
• Cross-site scripting (XSS): Injects scripts into web pages viewed by other users.
• Sideloading: Installing an application from outside the official app store. It may install unauthorized apps, but it does not generally unlock the operating system or enable restricted system features.

• Geo-redundant storage (GRS) replicates data to a secondary Azure region, but the secondary copy is normally unavailable for read access.
• RA-GRS provides geo-replication and read-only access to the secondary region, satisfying all requirements.
• Zone-redundant storage (ZRS) replicates data across availability zones within the same Azure region, not separate geographic regions.
• Locally redundant storage (LRS) keeps copies within a single datacenter or region and does not provide geographic resiliency.

• Internal interface ? connected toward the corporate network/internal firewall
• External interface ? connected toward the Internet-facing firewall

1. A route for the internal corporate network through the internal-facing interface/firewall.
2. A default route (0.0.0.0/0) through the Internet-facing interface/firewall.

• Personally identifiable information (PII) detection

• Prompt Shields

• Self-harm content filtering addresses self-harm-related content.
• Violence content filtering addresses violent content.
• Neither protects customer PII or detects document-based prompt injection.

kusto 
Event 
| summarize make_set(EventID) by Computer

• summarize groups records.
• by Computer creates one result row per virtual machine.
• make_set(EventID) returns an array containing unique event IDs for that computer.

kusto 
| summarize make_list(EventID) by Computer

• Career enhancement — A mentor can provide guidance, advice, networking support and help the mentee identify career opportunities.
• Support with new challenges — A mentor can help the mentee think through unfamiliar situations and develop confidence and practical solutions.
• Personal development — Mentoring can improve skills such as communication, leadership, decision-making and self-awareness.

• Solving all problems — The mentor supports and guides the mentee but should not take responsibility for solving every problem.
• Discipline would be dispensed if they make a mistake — Mentoring does not remove normal accountability or workplace consequences. Mistakes should instead become learning opportunities.

• Check whether the data is accurate, complete, and properly prepared.
• Confirm that the pattern is not caused by an outlier, data-quality problem, or modeling issue.
• If the data is valid, treat the result as a potentially valuable new business insight.

• A: A data scientist may help, but expert validation and data-quality checking come first.
• C: Filtering out inconvenient data risks hiding a valid insight.
• D: Einstein’s result should not be accepted without verification simply because it produced the finding.

• The explanation states that Traffic Analytics can be enabled by a user with one of these subscription-level roles:

• Question 34 — Network Contributor: Yes
• Question 35 — Owner: Yes
• Question 36 — Reader: Yes, according to the stated explanation and documentation

• Elicited and documented customer requirements
• Converted them into clear, measurable specifications
• Validated the requirements with the customer
• Used them as the basis for design, quality checks, and acceptance

• A: Requirements should reflect the customer’s needs—not the supplier’s standards.
• B: Iteration review planning does not replace proper requirements collection.
• D: A retrospective occurs after work is completed and is mainly for process improvement, not initial requirements definition.

• B — Increase provisioned concurrency for Lambda

• D — Refactor the Lambda functions

• E — Use Amazon RDS Proxy

• Code suggestions: Inline completions as you write code, such as lines, functions, or blocks.
• Chat: An interactive interface for asking questions, explaining code, generating code, and helping with debugging.

• Knowledge Base: Not listed as a standard Copilot Individual IDE feature in this context.
• Pull Request Diff Analysis: More closely associated with GitHub-based code review or pull-request features, not the core Individual IDE extension capabilities.

• Store privileged credentials securely
• Grant the consultant only the access needed
• Provide temporary or time-limited access
• Rotate passwords automatically
• Record or monitor administrator sessions

• TACACS+: Centralizes authentication and authorization, commonly for network devices, but does not primarily provide password vaulting and privileged-session control.
• SAML: Enables web-based federation and single sign-on, not privileged credential management.
• SSO platform: Reduces the number of passwords users need, but does not necessarily protect administrative credentials or control privileged sessions.
• Role-based access control (RBAC): Assigns permissions based on job roles, but does not by itself prevent password sharing or securely broker administrator access.

• Business
• People
• Governance
• Platform
• Security
• Operations

• Cloud financial management
• Portfolio and program management
• Risk management
• Data governance
• Compliance and oversight

• Equipment and hardware
• Facilities
• Inventory
• Backup media
• Supplies stored at an alternate or remote location

• Personal belongings of staff: Usually not organizational assets.
• DR line-item revenues: Revenue is a financial impact, not a physical asset.
• Cloud-based applications: These are primarily logical or information-processing assets, even though they depend on physical infrastructure.

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

1. Modify the database subnet NACL inbound rules to allow traffic from the new web subnet’s CIDR block on the MySQL port (3306).
2. Modify the database subnet NACL outbound rules to allow return traffic to the new web subnet’s CIDR block on the required ephemeral port range.

• NIDS: Monitors network traffic for suspicious activity and network-based attacks targeting the application or its supporting services.
• HIPS: Protects an individual host by monitoring processes, files, and system activity. It can help secure the web server, but it is not focused specifically on the application’s network attack surface.
• SIEM: Aggregates and correlates logs; it does not directly prevent attacks.
• Honeypot: A decoy system, not the primary protection for a production web application.
• Certificate revocation list: Deals with certificate trust, not application exploitation.

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

• Blue team: Defends systems, monitors activity, and responds to attacks.
• Purple team: Coordinates red- and blue-team activities to improve defenses.
• White team: Oversees or manages the exercise, including rules and scope.

• Microservices: An application-design approach that divides an application into smaller services. It does not inherently reduce the number of operating systems.
• Virtualization: Creates virtual machines, but each VM generally requires its own complete operating system. This improves isolation but does not minimize OS instances as effectively.
• Infrastructure as code: Uses code to automate infrastructure deployment and configuration. It improves consistency but does not determine how many operating systems are used.

• Basic: No technical or architectural guidance.
• Standard: Technical support, but not the required design-assessment service.
• Professional Direct: Provides advisory and architecture guidance.
• Premier: Provides it too, but is unnecessarily expensive for this requirement.

• Input feature distributions differ from training data ? Analyze dataset drift metrics

• Model accuracy drops without code changes ? Analyze dataset drift metrics

• Endpoint latency increases under load ? Investigate scaling and infrastructure metrics

• Online payment fraud
• Account takeover
• Fake account creation
• Suspicious transactions

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

• B: Moving the task may affect the critical path and should not be done before evaluating the planned response and impacts.
• C: Excluding a required task is not appropriate without formal analysis and stakeholder approval.
• D: Lessons learned and the risk log should be updated, but only after or alongside managing the immediate issue; updating them is not the first action.

• Reviewing security policies and standards checks whether controls are documented, not whether they work.
• Reviewing security logs may show that monitoring is occurring, but does not directly establish that preventive controls are effective.
• Analyzing technical security practices is broad and may assess implementation, but it is less objective than an actual controlled attack.

• Design/compliance effectiveness: policies, standards, and procedures
• Operational effectiveness: logs, records, and evidence that controls operate
• Technical security effectiveness: penetration testing or vulnerability testing

• SAMLRequest: the SAML authentication request
• RelayState: the original destination or application state

• RedirectURL: not the standard SAML parameter for preserving the original request.
• DisplayState: not a standard SAML SSO parameter.
• StartURL: Salesforce-related terminology, but not the standard parameter used in this SAML exchange.

• A. IDS attack signatures: Primarily detects suspicious network activity, not necessarily malware embedded in uploaded files.
• C. Load balancer: Improves availability and distributes traffic; it does not inspect documents for malware.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection, but its primary role is not scanning uploaded PDFs for malware.

• Modelo de embeddings multimodal: transforma texto e imagens em vetores no mesmo espaço semântico. Isso permite comparar uma consulta textual com imagens, ou uma imagem com textos relacionados.
• Modelo generativo multimodal: interpreta diferentes modalidades e gera conteúdo, mas não é a escolha específica para indexação e busca vetorial.
• Modelo de geração de imagens: cria imagens, portanto é inadequado.
• Modelo de embeddings de texto: não atende consultas com imagens.

• Customer: Dual
• Date: Dual
• Sales: DirectQuery
• SalesAggregate: Import

• Sales – DirectQuery: Near-real-time data should not rely on an imported cache. DirectQuery sends queries to the source when visuals are loaded, allowing recent sales data to appear.
• SalesAggregate – Import: A weekly refresh is sufficient, and imported data generally gives faster visual performance because it is stored in Power BI’s in-memory cache.
• Customer and Date – Dual: These are dimension tables used with both the DirectQuery Sales table and the imported SalesAggregate table. Dual allows Power BI to use cached data when possible, while still behaving appropriately in queries involving DirectQuery data. This can improve performance and reduce unnecessary limited relationships.

1. Convert text and images into numerical embeddings.
2. Store or compare those embeddings.
3. Retrieve the most semantically similar items.

• Embedding model: Best for similarity search and retrieval.
• Generation model: Best for producing new text or other content from multimodal input.

• B: Trigger.Once + scheduled job

• C: 10-minute processing-time trigger

• A laptop
• Software access
• A password reset
• A mobile phone

• They run behind the scenes — applies more to automation or workflows.
• They are optional — catalog items are fundamental to a request-based catalog.
• They provide options — variables and variable options collect the requester’s choices for an item; they are not the catalog item itself.

• ARP poisoning: Redirects or intercepts local network traffic; monitoring would typically show suspicious ARP changes or man-in-the-middle behavior.
• Jamming: Interferes with wireless or radio signals. It would affect connectivity, not usually show a server-specific overload.
• Kerberoasting: Attempts to obtain and crack Kerberos service-account hashes; it does not normally cause a system outage.

• A single Construction Job can use multiple Machinery records.
• A single Machinery record may be used on multiple Construction Jobs.
• This is a many-to-many relationship, which Salesforce models using a junction object.
• The junction object can contain fields such as:

• Master-detail to Machinery
• Master-detail to Construction Job
• Date and cost fields

• Mesh: WAPs communicate wirelessly with one another, often to extend coverage without wired connections. It does not specifically describe centralized WLC management.
• Point-to-point: Connects two specific devices or locations.
• Ad hoc: Wireless devices communicate directly with one another without an access point.

• CCTV system — Detective control: Cameras monitor and record activity, helping identify or investigate security incidents after—or while—they occur.
• Signs about being filmed — Deterrent control: The signs discourage people from attempting unauthorized or criminal activity because they know surveillance is present.

• Preventive: Stops an incident from occurring, such as a lock or access-control system.
• Corrective: Restores systems after an incident.
• Directive: Instructs people to behave in a certain way, such as a security policy.
• Compensating: Provides an alternative control when the preferred control cannot be implemented.

Simple explanation

• The Azure VPN gateway to connect to
• Authentication settings
• Routes for networks that the client can access

• Looking up accounts, contacts, and opportunities
• Logging calls and updating Salesforce records
• Accessing previously available customer information when temporarily offline

• Salesforce Touch App: Primarily an older tablet-focused experience, not the best general solution for the sales team.
• Custom hybrid app: Unnecessary development when Salesforce provides the required capabilities natively.
• SalesforceA: Intended mainly for Salesforce administrators, not sales representatives.

• C — Schema.describeSObjects(new String[]{myObject})[0].fields.getMap()

• D — Schema.getGlobalDescribe().get(myObject).getDescribe().fields.getMap()

• A: sObjectType is not used this way, and fieldSet() is not the appropriate method for retrieving all fields.
• B: mySObject.myObject is not valid dynamic Apex syntax.

• SharePoint search: Finds documents based on search terms, but it does not reliably identify every 32-character account number for DLP enforcement.
• A hunting query in Microsoft 365 Defender: Used for security investigations, not for defining sensitive content in a DLP policy.
• Azure Information Protection: Uses classification and labeling; it does not automatically identify this specific account-number pattern unless configured with a matching sensitive information type.
• RegEx pattern matching: Best suited for structured identifiers with a known format, such as account numbers, employee IDs, or policy numbers.

• 25 — Traditional SMTP server-to-server delivery; often restricted for client submission and not inherently encrypted.
• 110 — POP3 for retrieving email; unencrypted by default.
• 143 — IMAP for retrieving and synchronizing email; unencrypted by default.
• 587 — Authenticated SMTP submission, commonly secured with STARTTLS.

• View/inspect configuration: Possible.
• Modify the installed application or its S-Controls: Typically restricted in a test-drive org.

• A: Daily involvement is unnecessary and may not solve the availability problem.
• C: Clarifying all requirements at the start conflicts with agile’s iterative refinement.
• D: Simply reviewing based on availability leaves the problem unresolved and allows rework to continue.

• Numerical flexibility: Adjusting the number of employees, such as using temporary, part-time or contract staff.
• Temporal flexibility: Varying when employees work, such as through flexitime, overtime or different working hours.
• Shift system flexibility: Changing work patterns or shift arrangements; it is not specifically about moving between tasks.

• SAML: Enables federated authentication and single sign-on between the IdP and SaaS providers.
• OAuth tokens: Allow delegated application access; OAuth is not primarily the first step for employee SSO.
• Password vaulting: Stores or autofills multiple passwords but does not eliminate the separate credentials or provide true federation.

• Identified risks
• Risk owners or responsible parties
• Likelihood and impact
• Risk response plans
• Current status
• Risk thresholds or trigger conditions

• Risk tolerance: The amount and type of risk an organization is willing to accept; it is not primarily a tracking document.
• Risk transfer: Moving the financial or operational impact of a risk to another party, such as through insurance or outsourcing.
• Risk analysis: The process of evaluating a risk’s likelihood and impact.