IIA IIA-CIA-Part3 Exam Prep
Certified Internal Auditor - Part 3, Business Analysis and Information Technology (Page 30 )

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

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

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

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

• Correct answer: C) After installing ES on the search head(s) and running the distributed configuration management tool.

• ES requires the Splunk_TA_ForIndexes.spl add-on on indexers to apply index-time configurations. It should be deployed via the distributed configuration management (DCM) flow after ES is installed on the search heads, so the indexers receive the proper configuration in a controlled, versioned bundle.

• A) Deploying when adding apps to the deployment server isn’t the ES-specific order; it bypasses the ES-instantiated workflow.
• B) Installing Splunk_TA_ForIndexes.spl first isn’t the recommended order; ES needs to be installed on the search heads first.
• D) It isn’t limited to indexer cluster sites or cluster master commands; the standard flow uses DCM to push the TA to indexers in general.

• Windows 10 VMs
• Windows Server 2012 or later VMs
• Running VMs—they do not need to be shut down
• Debian 8.2+ VMs, assuming the specific version is supported
• Stopped or deallocated VMs

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

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

• Automation handles repetitive tasks, and orchestration coordinates responses across tools (SIEM, SOAR, EDR, etc.).
• This allows the security team to process more events with the same number of people, improving throughput and response times.
• Analysts can focus on more complex tasks like investigation and threat hunting instead of manual triage.

• It increases complexity: automation can reduce complexity when well-implemented; complexity is not the main intended benefit.
• It removes technical debt: automation/OR focuses on current incident response efficiency, not primarily on architectural debt.
• It adds additional guard rails: governance is important but not the core value of automation/orchestration within a SIEM.

• Product Owner: May attend, but is not required unless also working as a Developer.
• Scrum Master: May attend to help facilitate or coach, but is not required.
• Developers: Must participate because the event is specifically for them.

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

• The correct permission is Manage Sandboxes (the official Salesforce name; the option in the list is written as “Manage Sandbox,” which is effectively the same idea but the canonical name uses the plural).
• Why: Sandboxes are a lifecycle feature. Only users with the explicit Manage Sandboxes permission can perform create, delete, refresh, or activate actions.
• Why the other options aren’t correct:

• Correct answer: D (Special category data)

• Why:

• Quick notes:

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

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

• Sustainability
• Performance efficiency
• Reliability

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

• Why: The data is unlabeled, so you can’t train a model with known input-output pairs. Unsupervised learning discovers structure in the data by grouping similar customers into clusters or tiers without labels.
• What it does: Clustering and segmentation (e.g., k-means, hierarchical clustering, DBSCAN, Gaussian mixtures) to form meaningful groups.
• Why the other options aren’t as suitable:

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

• Primary and core nodes: Use On-Demand Instances because the workload is business-critical. These nodes manage the cluster and store/process HDFS data.
• Task nodes: Use Spot Instances in an instance fleet. Task nodes are suitable for interruption because they do not hold essential cluster data and can be replaced or diversified across instance types.
• Terminate the entire cluster after processing: The job runs only about six hours each morning, and EMRFS stores data in Amazon S3. Keeping the cluster running for the rest of the day would waste money.

• A: Using Spot for primary and core nodes risks interruption of the critical cluster.
• C: All On-Demand is reliable but unnecessarily expensive; terminating the cluster helps, but Spot task nodes provide greater savings.
• D: Leaving primary and core nodes running after the task finishes continues to incur costs. Savings Plans also are less appropriate for this intermittent workload.

• A: True. You can change the size of a Virtual Warehouse after creation (via UI or ALTER WAREHOUSE).

• B: True. A warehouse can be resized while it’s running; the resize will take effect without needing to stop queries.

• C: True. A warehouse can be configured to suspend after a period of inactivity (AUTO_SUSPEND).

• D: True. A warehouse can be configured to auto-resume when new queries are submitted (AUTO_RESUME).

• Batch processing, such as scheduled data transformations
• Streaming processing, such as continuously ingesting events

• Manipulating data with multiple languages: Mainly a benefit of Databricks and Spark.
• Real-time notebook collaboration: A workspace/notebook feature.
• Alerts for query failures: A Databricks SQL or job-monitoring feature.
• Distributing complex operations: Primarily a Spark compute capability.

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

• Correct answer: UBA (A)

• Why: UBA (User Behavior Analytics) analyzes user activity, builds baselines of normal access patterns, and flags deviations (e.g., accessing sensitive projects not related to the user’s role). This insider-threat detection is exactly what the scenario requires.

• Why not the others:

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

• Secure: uses encryption, such as HTTPS or SFTP.
• Cross-platform: supported by many languages and operating systems.
• Internet-friendly: designed to communicate across networks, usually using standard Internet protocols.

• JSON/REST over HTTPS — widely supported, secure, and Internet-friendly.
• SOAP over HTTPS — also secure and highly cross-platform, though more heavyweight.
• XML over SFTP — secure file-based exchange, but it is not an API-style interface.

• Incidents & alerts — see how the phishing activity was detected, correlated, and investigated.
• Threat Explorer — search for the malicious messages, recipients, URLs, attachments, and campaign activity.
• Email and collaboration reports — assess how many users or messages were affected.
• Remediation details — verify whether messages were quarantined, removed, or otherwise contained.

• Microsoft 365 admin center — general tenant administration.
• Microsoft Entra admin center — identity and access management.
• Exchange admin center — mail-flow and Exchange configuration, rather than full phishing-incident investigation.

• According to the provided answer key, the four options are: Upload File, User Criteria, HR Profiles, HR Criteria (options B, D, F, G).

• Upload File: Filter by a file you upload (e.g., CSV) that provides data for bulk case creation.
• User Criteria: Filter by criteria related to users (e.g., role, department) to select target users.
• HR Profiles: Filter by HR profile data associated with users.
• HR Criteria: Filter by HR-related criteria or attributes.

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

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

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

• A private IP address on the virtual network
• An associated public IP address

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

• The problem: Guest users can’t create posts in the Monthly Reports channel.
• The recommended fix (answer B): Modify the Guest access settings in the Teams admin center.

• Guest access settings control what guests are allowed to do across Teams (for example, posting, chat, and channel participation). If guests are restricted from posting, enabling the appropriate guest permissions will let them post in channels like Monthly Reports.
• The other options don’t directly change guest permissions in the way that affects posting:

• Global Unicast: These are the IPv6 addresses that are globally routable on the Internet. They’re allocated by Regional Internet Registries (RIRs) and can be reached from anywhere with proper routing (similar to IPv4 public addresses). Example ranges include 2000::/3.

• Link-local: fe80::/10. Used only on the local link; not routable beyond the directly connected network.

• Unique Local Addresses (ULA): fc00::/7. Private addresses for internal use within an organization; not publicly routable on the Internet (like IPv4 private addresses).

• Multicast: ff00::/8. One-to-many addresses used for group communication, not unicast routing.

• Correct answer: D — use the same hashing algorithm as the sender's to create a numerical representation of the file.

• Integrity is verified by recomputing the hash on the received data and comparing it to the sender’s hash. This must use the same hash function; if you use a different algorithm, the digests won’t match even if the data is intact.
• The hash output is a fixed-length digest (a numerical representation). Whether you call it a “binary image” or a “numerical representation,” the key is that you generate the same type of digest with the same algorithm and compare them.

• A: same algorithm but the result is described as a binary image instead of a digest; you still compare the digest, but the phrasing is less precise.
• B/C: using a different algorithm would produce a different digest, causing false mismatch or failure to verify integrity.

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

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

• Key concept: ALE = SLE × ARO

• SLE = $15,000
• Occurrences: 2 in 3 years ? ARO = 2/3 per year ˜ 0.6667

• ALE = $15,000 × 0.6667 ˜ $10,000 per year

• ALE is the expected annual loss, so it averages the losses over each year.
• This helps prioritize risk treatments by comparing ALE to the cost of controls.

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

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.

• The correct option is A: Data architecture.

• Why: In the AWS CAF, the Platform perspective covers the technical foundation and architecture that enable cloud workloads to run reliably and efficiently. This includes how data is modeled, stored, and accessed across the enterprise—the core of data architecture.

• Quick mapping for the other options:

Simple explanation

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

• 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

• A? ??? Aurora Replicas? ?? ??? ???? ?? ???, ?? ???? Network Load Balancer(NLB)? ??????. NLB? ?? 4 ?? ???? HTTP ??? ?? ???(Sticky sessions)? ????? ???? ????.
• ??? ?? ??????? ?? ?? ???? ??? ???? ?? ????? ????? ?? ?? ???(?? ?/??? ??)? ?????. ? ??? ALB?? ?? ????, NLB?? ???? ?????.
• ??? ??? ??? ??? ???? ?? ???? ???? HTTP ???? ??? ALB? ???? ???. A? ? ??? ??????.

• Assign users or their team an appropriate security role.
• Ensure the role has the required table privileges, such as read, create, write, and append.
• Share the app with that security role in the app designer.

• Dynamics administration center: Used for environment and service administration, not routine app access configuration.
• Manage Roles: Not the specific Dataverse area used to define app and data permissions.
• Security Roles: Define what users can access and which operations they can perform.

• Help the team identify the causes of delays.
• Encourage continuous improvement through retrospectives.
• Support the team in changing its process, tools, or collaboration methods.
• Help remove impediments that the team cannot resolve independently.

• A: An impediment log may help, but simply maintaining it does not ensure the impediments are resolved.
• B: Directing the team to solutions conflicts with agile self-management.
• C: Adding impediments to the product backlog could delay their resolution and treats them like product features.

• In the AWS shared responsibility model, AWS manages the security of the “infrastructure,” including the physical hardware and underlying virtualization.
• The customer is responsible for everything else in the cloud stack: the guest OS on EC2, the NoSQL database software running on it, data, patching the OS, and configuring access controls like security groups.
• So, for a self-managed NoSQL database on EC2, AWS would handle the physical hardware, while you would patch the guest OS and manage DB availability, backups, and security.

sql 
GRANT ALTER ON SCHEMA::schemaA TO User1;

• TRUNCATE TABLE is a DDL operation, not a normal DELETE.
• Having DELETE permission on a table is not sufficient to truncate it.
• The minimum relevant permission is ALTER on the table.
• Granting ALTER on SCHEMA::schemaA allows the user to truncate tables within schemaA.
• It does not grant equivalent permissions on schemaB or schemaC, satisfying least privilege.

• Answer: C (192.168.0.1-192.168.0.99, 192.168.0.101-192.168.0.254)

• Why: The interface is 192.168.0.100/24, so DHCP pools must be within the 192.168.0.0/24 subnet and cannot include the router’s IP (192.168.0.100), the network address (192.168.0.0), or the broadcast (192.168.0.255). Option C provides two ranges that exclude those addresses.

• Why the other options are invalid: