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

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

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

• Correct answer: D (Special category data)

• Why:

• Quick notes:

• IKE: Negotiates security parameters for IPsec VPNs; it does not identify switch ports.
• VLAN: A logical network segmentation method, not a discovery protocol.
• netstat: Displays local network connections and listening services, but cannot identify the physical switch or port.

• Data lakes: scalable, low-cost storage for structured, semi-structured, and unstructured data.
• Data warehouses: reliable SQL analytics, governance, and performance features.

• Data lake: Primarily provides flexible, scalable storage but may lack warehouse-style reliability and governance.
• Data warehouse: Strong for structured analytics but less flexible for raw and unstructured data.
• All of these: The individual lake and warehouse do not, by themselves, unify the siloed architecture.

• Answer: C — Spot Instances

• Why: The workload is a test environment that can be interrupted and does not need to run continuously. Spot Instances let you bid on unused EC2 capacity at a deep discount, making them the most cost-effective option for interruptible workloads.

• Why not the others:

• Quick tips:

1. Ingestion Lambda receives requests from API Gateway and places messages in an SQS queue.
2. Processing Lambda is triggered by the queue and loads records into Aurora PostgreSQL.

• Decoupling: API request handling is separated from database loading.
• Buffering: SQS absorbs bursts when incoming traffic exceeds the database’s processing capacity.
• Controlled concurrency: Configure the SQS-triggered Lambda’s concurrency and batch size to avoid overwhelming Aurora or exhausting database connections.
• Automatic retries: Messages that fail processing can return to the queue and be retried. A dead-letter queue can capture persistent failures.
• Lower operational effort: The solution remains serverless and avoids managing EC2 servers or Kubernetes clusters.

• A: EC2 and Tomcat add server-management overhead.
• B: DynamoDB/DAX would require changing the database model and does not solve the Aurora ingestion design.
• C: SNS is useful for notifications and fanout, but SQS is better for durable buffering and backpressure in this producer-consumer workflow.

• Amazon S3 — Object storage, not a database.
• Amazon DynamoDB — Fully managed NoSQL key-value and document database.
• Amazon Redshift — Managed data warehouse designed for analytics, not primarily transactional MySQL workloads.

• Why: Crisis management relies on established, repeatable procedures for responding to an incident (activation of the crisis team, escalation paths, communications, containment actions). This ensures a coordinated, timely, and auditable response.

• Why not the others:

• Why: ADS is designed to collect information about on-premises environments to plan migrations. It inventories details like hostname, IP address, MAC address, OS, hardware, and installed software, plus dependency mappings. This data helps you understand your current environment before moving to AWS.

• How it differs from the other options:

• Practical use: Install the ADS agent on on-prem hosts to collect data, then view the inventory in Migration Hub to inform migration planning and sequencing.

• nomes de pessoas;
• organizações;
• locais;
• datas;
• números de processos;
• leis ou contratos.

• NER = identifica informações específicas e classificáveis.
• Sumarização = reduz um documento e apresenta seus pontos principais.

• The two correct options are:

• The two incorrect options:

Why

cmd 
PowerShell.exe -ExecutionPolicy Bypass -File C:\Scripts\ConfigureVM.ps1

Why the other options are less suitable

• GPO logon script: Runs only when a user logs on and may not run during initial VM provisioning.
• GPO startup script: Can work, but requires the VM to be joined to the domain and the policy to be applied. It is also normally evaluated at each startup.
• Place scripts in a VHD: Merely placing scripts on a disk does not cause them to execute.

• Correct answer: A. Email templates

• Snippets are reusable content blocks that you insert into email content, and they require an email template (or at least an email draft) to render.
• You can store region-specific footers as snippets and include them in a template, but there would be nothing to render the snippet into without a template.
• The other options aren’t prerequisites for using snippets:

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

1. Create a new AMI or copy the existing AMI while specifying EBS encryption and an appropriate AWS KMS key.
2. This creates an encrypted AMI backed by encrypted EBS snapshots.
3. Copy the encrypted AMI to the destination Region, using a KMS key available there.
4. Launch the application stack from the encrypted AMI.

• B: AWS KMS does not encrypt an existing unencrypted AMI in place. You must create an encrypted copy.
• C: AWS Certificate Manager manages TLS certificates, not EBS or AMI encryption.
• D: Enabling encryption by default affects newly created EBS volumes and snapshots; it does not encrypt an existing unencrypted AMI during copying.

• Multiple nodes: Data is replicated several times in the primary region.
• Separate geography: A copy is asynchronously replicated to a secondary Azure region.
• Readable secondary: RA-GRS provides read-only access to the secondary replica, even when the primary region is available.

• GRS: Replicates to another region but the secondary copy isn’t normally readable.
• ZRS: Replicates across availability zones in the same region, not a separate geographic region.
• LRS: Keeps replicas within a single datacenter or region and provides no geographic redundancy.

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

• In the source query: apply UPPER() or LOWER() to the column.
• In Power Query Editor: use Text.Upper or Text.Lower on the column, then load.

• This fixes the root cause when comparisons/joins depend on case.
• In DirectQuery, transformations are pushed to the source or query layer; ensure the transformation is supported by your data source/connector.
• After normalization, verify relationships and any downstream visuals that rely on that column.

• Answer: C – netstat -an

• netstat -an lists all active connections and listening ports with numeric addresses, without resolving names. This lets you spot DoS patterns such as a flood of connections to a specific port or many connections from a single or few IPs.
• The other options don’t help as directly:

• Windows: netstat -an and look for numerous ESTABLISHED connections to a service or many SYNs to a port.
• Filter by port, e.g., netstat -an | findstr :80, or on Linux: ss -tunap | grep ':80'.

• Netstat provides a snapshot. DoS detection often benefits from continuous monitoring, flow data, and IDS/IPS logs.

• Azure Resource Manager templates: Use ARM templates to define the VM infrastructure and baseline configuration as code. This ensures all Windows Server 2016 VMs are created with a uniform setup, minimizing manual configuration.

• PowerShell Desired State Configuration (DSC) extension for Windows: DSC enforces a defined state across all servers and can automatically remediate drift. This keeps the VMs in the desired configuration with minimal ongoing admin effort.

• S3 Versioning stores all versions of an object. If an object is overwritten or deleted, you can recover the previous version using its version ID.
• This protects against accidental deletion or overwriting because the original data remains accessible as an older version.
• How to enable:

• Practical notes:

• S3 Lifecycle rules: automate moving/expiring data, not specifically protection against deletion.
• S3 bucket policies: control access but don’t inherently preserve previous data.
• S3 server-side encryption: protects data at rest, not against deletion/overwrite.

• Network Security Groups (NSGs) control network traffic to and from Azure resources.
• By applying NSGs to the web tier and the database tier (subnets or NICs), you can:

• NSGs provide the necessary granularity (source/destination, port, protocol) to enforce the desired traffic patterns between tiers.
• For easier management you can use separate subnets for each tier or, optionally, use Application Security Groups to simplify rule management.

• In Azure, the typical cost approach for pay-as-you-go VMs is an Operational Expenditure (OPEX) model. You’re billed for actual usage each month.
• The term “elastic expenditure model” isn’t a standard Azure cost category. Elasticity describes scaling capacity, not the billing category itself.
• So recommending the elastic expenditure model is not correct for this goal.

• The solution does not meet the goal. Answer: No (B).

• Pay-as-you-go aligns with OPEX because costs vary with usage.
• Elasticity is about scaling resources, which affects performance and capacity, not the fundamental cost model.

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

• What it’s asking: In an ARM template, for an Availability Set, what value should you set for the property platformFaultDomainCount to maximize availability during fabric failures or maintenance?

• Key concept: Fault domains are groups of hardware that can fail independently. By spreading VMs across more fault domains, you reduce the risk that a single hardware fault takes out many VMs.

• Important detail: For managed Availability Sets, the number of fault domains you can use varies by region — typically 2 or 3.

• What to choose: Set platformFaultDomainCount to the maximum supported in your region. In most regions this is 3, which gives you the best resilience. If your region only supports 2, you’d use 2.

• Answer: 3 (Max Value). In ARM template syntax, this would appear as "platformFaultDomainCount": 3 (within the Availability Set resource).

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

• The mapping and resolution of endpoint identities (EIDs) to their location (RLOCs) in an SD-Access fabric is handled by the control plane using the LISP protocol.
• Why not the others:

• Recovery procedures actually work
• Recovery time and recovery point objectives can be met
• Staff understand their responsibilities
• Contact details, dependencies, and technical configurations are accurate
• Gaps or conflicts exist in the plan

• Not version-controlled: Creates a risk of using an outdated copy, but the plan might still be effective.
• Contact information needs updating: This is a specific weakness that can be corrected, often identified during testing.
• Not approved by senior management: Approval is important for authority and resource commitment, but an untested plan presents the most direct risk that recovery will fail when needed.

• Answer: D) Out-of-band management

• Why this is correct:

• Why the other options aren’t suitable here:

• The app on EC2 connects to Aurora using DB credentials stored on the instance. Secrets Manager centralizes these credentials and can rotate them automatically, eliminating manual updates on each EC2 host.
• Automatic rotation reduces operational overhead and enhances security because credentials are rotated on a schedule without code changes.
• The app can retrieve the current secret at runtime (e.g., via the AWS SDK) and use it to authenticate to Aurora, avoiding reliance on locally stored files.

• B (Parameter Store) can store secrets but lacks seamless built-in rotation for database credentials like Secrets Manager; rotation often requires more custom work.
• C (S3) would require complex tooling to rotate and securely fetch credentials and still risks exposure if access policies aren’t perfect.
• D (Encrypted EBS volumes) would store credentials locally on each instance and does not automate rotation or centralized management.

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

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

• AWS IoT Greengrass supports local ML inference using models trained in Amazon SageMaker.
• The model and inference code run on the factory’s local server, so processing continues even when internet connectivity is unavailable.
• A Greengrass component can:

• This provides low latency and avoids sending images to AWS for every inference.

• A: Uses AWS-hosted services and therefore depends on internet connectivity. It would fail during an outage.
• C: Snowball Edge is unnecessary for this use case and adds deployment complexity. A local Greengrass server is the intended edge-inference solution.
• D: Amazon Monitron is designed for monitoring industrial equipment health, not analyzing camera images with a custom SageMaker model.

• App Tag: a label that reflects the app’s enterprise readiness based on its Cloud Confidence Index (CCI) rating. It lets you quickly group apps (e.g., Poor, Average, Good) for policy decisions.
• App Score: a numeric value representing the CCI score. It provides a precise threshold you can use to enforce policies (e.g., block apps with Score below 50).

• You can create policies that block or restrict apps with a Poor App Tag or with an App Score under a chosen threshold.
• These two aspects let you filter cloud apps by CCI ratings during policy evaluation.

• CCL isn’t described as a real-time policy facet in this scenario.
• GDPR Readiness is a separate consideration and not the two CCI aspects used for real-time protection policy in this context.

• The Accrue liability on product receipt flag controls whether a liability is accrued and posted at the time of receiving the item.
• If this checkbox is unchecked, receipts won’t create postings to the Product receipt journal. Enabling it ensures the system posts inventory value and the vendor liability when the item is received.

• Go to the Item model group setup form.
• Enable (check) Accrue liability on product receipt.
• Save.

• The other option, Include physical value, affects how physical value is handled but is not the direct cause of postings to the product receipt journal. If issues persist after enabling accrual, you may need to verify related posting definitions or journal setup.

• Use a field on Account to show the aggregated yearly shipments (a Roll-Up Summary).
• A Master-Detail relationship between Shipment and Account is required for Roll-Up Summary to work (and to ensure access is governed by the parent Account).
• OWD and the relationship type determine what users can see. If you want to restrict shipment-level access while still showing a summary on Account, Private OWD on Shipment plus Master-Detail helps, because access to shipments is controlled by the Account record.

• A (Public OWD on Shipment with Process Builder and a Lookup to Account): Not ideal. Public access would expose shipments broadly, and a lookup cannot support a built-in roll-up summary.
• B (Private OWD on Shipment, Roll-Up Summary, Master-Detail to Account): Best answer. Private shipments, but because of Master-Detail, access and the roll-up are tied to the Account. The Account can show the yearly total via a Roll-Up Summary field.
• C (Controlled by Parent on Shipment, Trigger, Master-Detail): Master-Detail is correct, but using a trigger is unnecessary for a straightforward roll-up; roll-ups are the standard, maintainable solution.
• D (Private OWD on Shipment, Trigger, Lookup to Account): More complex and not as efficient; no automatic roll-up, and lookup breaks the ease of summarizing by Account.

• IaaS: You manage the virtual machine’s operating system, configuration, applications, and data. Azure manages the physical infrastructure and virtualization platform.
• PaaS: You deploy applications without managing the underlying operating system or servers.
• SaaS: You consume a complete application managed by the provider, such as Microsoft 365.

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

• Program and project management
• Risk management
• Cloud financial management
• Data governance
• Portfolio management

• Sustainability
• Performance efficiency
• Reliability

• Create a record-triggered Flow on Opportunity.
• Run it when the record is created or updated.
• Add entry criteria such as Probability > 50%.
• Use Create Records to create the related Sales Demo Request, populating its Opportunity lookup.

• Apex Trigger: Possible, but unnecessary custom code for a straightforward automation requirement.
• Workflow Rule: Cannot create a related custom record.
• Process Builder: Could create a record, but Flow is Salesforce’s preferred and more capable declarative automation tool.

• Use one Azure AD directory for the organization.
• Separate divisions with subscriptions and/or resource groups.
• Assign each division’s administrator appropriate Azure role-based access control (RBAC) permissions, scoped to their subscription or resource group.

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

• IPsec: Protects traffic at the network layer, commonly for VPNs; it is not WPA2’s authentication protocol.
• SSL: Protects specific application sessions and has largely been replaced by TLS.
• SSH: Secures remote command-line administration.

• ProductSearchModel.getProductSearchHits() — option C
• ProductSearchHit.getRepresentedProducts() — option B

• ProductMgr.queryAllSiteProducts() (A) queries every product in the site, which is heavy and not scalable for large catalogs.
• Category.getProducts() (D) retrieves all products in a category; this can be slow for large categories.
• Using the search model and hits (B and C) leverages the search index, supports paging, and avoids scanning the entire catalog, making it more scalable.

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

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

• B — AWS DataSync: Transfers data between storage systems, such as S3, file systems, and on-premises storage. It is not a marketplace or catalog for third-party datasets.
• C — Kinesis Data Streams and CodeCommit: CodeCommit is a source-code repository, not a third-party data provider. Kinesis is for streaming data ingestion.
• D — Kinesis Data Streams and ECR: ECR stores container images, not datasets. Kinesis does not provide access to ECR data as an external dataset source.

• Correct answer: C. AWS CloudFormation

• Why: CloudFormation lets you define infrastructure as code via templates (JSON or YAML). You can create a single template that describes multiple AWS resources and reuse it to deploy consistent stacks across environments. Templates can be parameterized and stored for repeated deployments. Other options (Marketplace, AMI, OpsWorks) don’t provide reusable deployment templates in the same way.

• Domeny tworza restrykcjony razem z typem. Wykorzystujesz je w kolumnach, aby miec spójna walidacje danych w wielu miejscach.
• To nie jest pelny niestandardowy typ z wlasnym input/output funkcjonowaniem. Aby stworzyc typ z wlasnym I/O i operacjami, uzylbys CREATE TYPE (lub rozszerzen w C). Domeny to uproszczona forma ograniczen na istniejacy typ.

• CREATE DOMAIN positive_int AS integer NOT NULL CHECK (VALUE > 0);
• CREATE TABLE orders (id serial, qty positive_int);

• latwo wymuszaja wspólne reguly dla wielu kolumn/naglówków,
• zmiana regul w jednym miejscu (domena) automatycznie wplywa na wszystkie kolumny ja uzywajace.

• The correct answer is D: All of the above.

• Snowflake Web Interface (UI): You can create and manage Virtual Warehouses from the UI (resize, suspend/resume settings, etc.).
• SQL commands: You can create and alter warehouses with DDL like CREATE WAREHOUSE and ALTER WAREHOUSE.
• Data integration tools: ETL/ELT tools can create/manage warehouses by connecting to Snowflake and issuing the appropriate commands or using their config to specify a warehouse.