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

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

• Ensure that only users who manage the production environment sign in to the Azure portal from a hybrid Entra-joined device and authenticate with MFA.

• Use Microsoft Entra ID Protection (Identity Protection) to enforce MFA enrollment:

• Update the existing Capolicy1 (a Conditional Access policy):

• Identity Protection MFA registration policy ensures users are enrolled in MFA (Box 1 choice).
• CA policy Capolicy1 with aGrant control of “Require MFA” enforces MFA during sign-in (Box 2 choice).
• Both work together with the hybrid-joined device requirement to satisfy the authentication/authorization rules.

• Apply the MFA registration policy to the production-management users.
• Apply the MFA grant to Capolicy1 for those same users/groups.

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

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

• Answer: S3 Inventory report.

• Why: The S3 Inventory report provides a scheduled listing of objects within a bucket, including metadata about each object. When you configure it to include object tagging, you can see tags for each object, and the object keys (which reflect prefixes) and bucket scope are captured in the report. This makes it suitable for auditing and tracking “tags, buckets, and prefixes” across S3 objects.

• What the other options do (not suitable for this purpose):

• Tip: If you need tags in the report, enable the inventory option to include object tagging in the configuration.

• Answer: B — Improve employee training and awareness

• Why this is correct:

• Why the other options are less effective here:

• Quick practical note:

• Correct answer: C — The model is deployed at UK border checkpoints.

• The EU AI Act applies to AI systems used within the EU or by entities established in the EU. So:

• Improve QA testing efficiency: A prototype may help discover defects early, but that is not its greatest benefit.
• Decrease time allocated for user testing and review: Prototyping usually requires additional user involvement and review, not less.
• Minimize scope changes: Prototypes can actually reveal new requirements or cause scope changes. However, discovering those changes early is beneficial.

• What the dataflow options mean:

• Why C fits best:

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

• You provision the virtual machine.
• You manage the guest operating system, applications, and configuration.
• Azure manages the physical servers, datacenter, and underlying virtualization infrastructure.

• Two VMs
• Distributed across two separate availability zones

• Correct answer: B) Context window.

• Why: The context window is the number of tokens the foundation model can process in a single inference. It sets the maximum length of the combined input (prompt) and the model’s output. A larger context window allows more content to be included in one prompt.

• How to use: Check the FM’s context window value and ensure your prompt length plus the desired completion stays within that limit. If needed, summarize or split input across multiple prompts.

• Why the other options aren’t correct:

• Quick tip: Verify the specific FM’s context window for Bedrock, since different models have different token limits.

• Answer: Record Producer (option D)

• Why: In ServiceNow HR Service Delivery, to make an HR Service usable from the Employee Service Center (self-service portal), there must be a way for employees to submit the request. A Record Producer provides the employee-facing form that creates the underlying HR Case when submitted. Without a linked Record Producer, the HR Service wouldn’t offer a submit form in the Employee Center.

• What the other fields are generally for (not required for exposure):

• Quick check: Look at the HR Service definition and ensure a Record Producer is associated so employees can submit requests from the Employee Center.

• Failed login attempts
• The account being targeted
• The source user or system
• Time and frequency of attempts

• Two-factor authentication: Helps prevent unauthorized access, but does not primarily detect the employee’s attempts.
• Firewall: Controls network traffic; it generally does not monitor individual login attempts.
• Intrusion prevention system (IPS): Can detect certain network attacks, but this scenario is best addressed through authentication and audit logging.

• Short answer: The correct term is Anti-forensics (option D), not “Felony.”

• Why: The actions described—hiding files in slack space, changing file headers, placing suspicious files in executables, and altering metadata—are classic anti-forensics techniques. They’re used to hinder or obscure forensic analysis, not to label the act as a legal category.

• About the options:

• Note: The provided answer key lists B (Felony), which is misleading for this exam objective. The exam typically tests knowledge of forensics concepts, where anti-forensics is the correct category.

• Correct answer: A — a clear business case has been established.

• The audit focus for IT procurement is ensuring there is a solid economic justification for the investment. A clear business case documents the expected benefits, costs, risks, and alignment with strategic objectives, which governs whether the investment is worth pursuing.
• The other options are important controls or project aspects, but they are secondary to ensuring the investment is justified financially and strategically:

Simple explanation

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

• The answer: Question 51: C — Request trigger.

• To invoke a Logic App from an external service (here, the Azure Application Insights availability test) you need a trigger that starts on an incoming HTTP request. In Logic Apps, this is the trigger that exposes an HTTP endpoint — typically shown as "When a HTTP request is received" and referred to as the Request trigger.
• The other options aren’t appropriate:

• Create a Logic App with the Request trigger to generate a URL.
• Configure Application Insights to post the degraded-availability payload to that URL.
• Add actions (e.g., send email, follow-up) in the Logic App to notify the customer services team.

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

1. Remote access to a Windows PC
2. Full chat and optional game-console functions

• Windows Remote Desktop (RDP) uses TCP 3389. The router needs a port-forwarding rule that sends incoming traffic on that port to the Windows PC’s internal IP address.
• The game console should connect through the wireless AP. Using WPA2-PSK provides the required wireless security while allowing normal online, chat, and optional services.
• The firewall should separate the internal network from the screened subnet. Its screened-subnet-side address is shown as 10.100.0.1.
• Devices must be placed in the correct network locations: the PC behind the router, the console on the wireless AP, and the firewall between the appropriate network segments.

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

• Answer: D. Select an IdP

• Why: To reduce the number of credentials across multiple SaaS apps, implement a single sign-on approach via an Identity Provider. The first step is choosing the IdP; once selected, you can enable SAML (A) or OAuth as supported by apps. Password vaulting (C) is not a true SSO solution, and B is not the foundational step.

• VMs without NGT: Not clearly a migration blocker on its own; NGT (Nutanix Guest Tools) status isn’t the typical gating factor for live migration during maintenance.
• VMs marked as an Agent: Not a standard, widely-known migration blocker; agents aren’t the typical reason a VM can’t be migrated.
• Memory Overcommitted VMs: While memory pressure can affect placement, memory overcommitment isn’t a fundamental reason a VM would be labeled non-migratable during maintenance.
• VMs with attached Volume Groups: This is the strongest candidate. A Volume Group is a set of volumes bound to a VM; moving the VM would entail relocating and reattaching those volumes, which can complicate or block live migration during maintenance.

• Reusing features across different models and teams
• Consistent feature definitions
• Managing feature versions and metadata
• Using features for both training and inference

• SageMaker Data Wrangler: Prepares and transforms data; it is not primarily a shared feature repository.
• SageMaker Clarify: Helps detect bias and explain model predictions.
• SageMaker Model Cards: Documents models, including intended use, risks, and evaluation results.

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

• Mapping:

• Why:

• Quick note: If you were to host a website on a VM, it would be IaaS; if you used a platform service instead of a VM, it would be PaaS. CaaS (containers) isn’t shown here.

• The Balanced Scorecard translates an organization’s vision and strategy into a set of concrete objectives and metrics across four perspectives (financial, customer, internal processes, learning & growth). This framework explicitly links IT goals to business goals and provides a way to measure and monitor alignment over time.

• Enterprise architecture (EA): Great for governance, standards, and roadmaps to ensure IT assets support business needs, but it’s more about structure and alignment at design time rather than directly measuring ongoing alignment of goals.
• KPIs: Useful metrics, but they don’t by themselves provide a full framework to ensure IT goals are aligned with organizational strategy.
• Enterprise dashboard: A visualization tool for metrics; it helps report status but doesn’t inherently establish or assess alignment.

• cloud applications only
• all Web traffic including cloud applications

• Cloud applications only: Only traffic to cloud apps is steered to Netskope for inspection/enforcement; other traffic bypasses.
• All Web traffic including cloud applications: All web-bound traffic, including cloud app traffic, is steered to Netskope.

• Browser isolation, Web traffic only, or a vague “traffic only” option are not the standard two steering modes.
• These two configurations let you decide what traffic Netskope analyzes in real time and what is bypassed.

• The “Answer(s)” field lists B and C (likely incorrect). The explanatory text correctly describes cloud applications only and all Web traffic including cloud applications as the two configurations.

• VPC: A logically isolated virtual network in a cloud environment; it describes networking, not shared application access.
• NFV: Replaces dedicated network appliances with virtualized network functions.
• SaaS: A cloud service model in which users consume an application without managing its infrastructure. It could describe how the application is delivered, but the question emphasizes serving multiple user groups, which points to multitenancy.

• Security Development Operations (SDO): a security-focused take on DevOps, integrating security into the development pipeline.
• Service Data Object (SDO): a data representation used in some middleware or enterprise apps.
• Software-Defined Overlay (SDO): a networking overlay concept.
• Secure Data Object: a generic data-security term.

• The requirement is a fully managed file server that natively supports Microsoft workloads and file systems and uses the SMB protocol. FSx for Windows File Server is built specifically for Windows workloads, provides native SMB file shares, and supports Windows permissions/Active Directory integration.
• Why the others don’t fit:

• The Act requires:

• It does not, as a public obligation, mandate publishing a detailed report on the training data used.
• Also, the Act does not specify a fixed “six months” retention for system logs in a way that would clearly make A required; logs for traceability are implied, but the six-month period is not a defined, universal requirement.

• IaaS: You deploy and manage virtual machines, operating systems, disks, and networking. Azure manages the physical datacenter and host infrastructure.
• PaaS: Azure manages the operating system and runtime so you can focus on deploying applications, such as with Azure App Service or Azure Functions.
• SaaS: You consume a complete, provider-managed application.

• 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

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

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

• Sustainability
• Performance efficiency
• Reliability

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

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.

• Port 515: LPD/LPR line-printer service
• Port 631: IPP — Internet Printing Protocol
• Port 9100: JetDirect/RAW printing, commonly used by network printers

• Linux machine: Linux could run these services, but the three printer-specific ports strongly indicate a printer.
• Router: Routers may use Telnet and HTTP, but normally would not expose ports 515, 631, and 9100 together.
• Windows machine: Windows can share printers, but this particular service combination is more characteristic of a network printer’s embedded operating system.

• A separate scope using a /32 subnet: A /32 identifies one host, but it is not a practical DHCP scope for this purpose.
• A static IP within the DHCP range: This can cause an IP address conflict if DHCP assigns that address to another device.
• SLAAC: Used for automatic IPv6 address configuration, not for assigning a predictable IPv4 address through DHCP.

• Why Ishikawa:

• Why not the others:

• Correct answer: A) Hashing

• Why: Hashing produces a fixed-size digest of the software. If the final build is altered in any way, the hash will change, enabling you to detect tampering by comparing the stored digest with a freshly computed one.

• Why not the others:

• TCP is connection-oriented. It establishes a connection before data transfer using a three-way handshake (SYN, SYN-ACK, ACK), enabling reliable delivery, ordering, and flow control.

• UDP is connectionless. It sends datagrams without a prior connection and provides no guarantee of delivery, order, or protection against duplicates; any reliability is up to the application.

• B incorrectly states UDP uses acknowledgment packets; UDP has no built-in ACKs.
• C wrongly claims UDP provides reliable transfer and that TCP is connectionless.
• D misstates framing bits; neither protocol uses the listed TCP/UDP handshake bits in frames.

• Correct answer: only new data added to the eventhouse (option E).
• Why: When you enable OneLake availability for the eventhouse, OneLake starts syncing data going forward. It does not automatically backfill or copy over data that already exists in the eventhouse before the enablement.
• What that means in practice: Any data added to the eventhouse after you enable OneLake will appear in OneLake (and be visible from OneLake file explorer). Pre-existing data in the eventhouse stays there unless you perform a separate backfill/copy operation outside the standard OneLake enablement.
• How to verify: add a small new dataset to the eventhouse after enabling OneLake availability, then check OneLake to confirm the new dataset appears.

• Multiple AWS accounts: Create a separate account for each department or workload. This provides clear isolation and makes it easier to track each department’s usage and costs for chargeback.
• Consolidated billing: AWS Organizations can combine billing for multiple accounts into one central payer account. The company can still view costs by account while managing payment centrally.

• Placement groups: Control how EC2 instances are physically placed for networking or performance; they do not provide departmental billing separation.
• Edge locations: Infrastructure used by services such as Amazon CloudFront; unrelated to chargeback.
• AWS Config: Records and evaluates resource configurations and compliance; it is not a billing-separation mechanism.

• Cross-account access is typically implemented with an IAM role. You create a role in the target account (where the resources live) and configure a trust policy that allows principals from the source account to assume that role.
• Users in the source account then assume the role (via Switch Role in the console or STS:AssumeRole) and receive temporary credentials with the role’s permissions to access the resources.

• IAM group: Groups exist inside a single account; they don’t grant cross-account access.
• IAM tag: Tags are metadata and do not grant access.
• IAM Access Analyzer: It analyzes and identifies public or cross-account access but does not grant access itself.

• Amazon Kendra is a managed enterprise search service that can index content stored in S3 and support natural-language queries to find text inside documents (PDFs, Word files, etc.).

• Rekognition analyzes images/videos, not document text search.
• Polly is a text-to-speech service.
• Lex is a chatbot service.

• Create a Kendra index.
• Add a data source of type S3 and point it to your bucket (with an IAM role that allows access).
• Configure/document conversion if needed, then index the data.
• Use the Kendra API or console to run natural-language queries against your indexed documents.

• Key difference: DirectQuery leaves data in the on-prem SQL Server and queries it live. That means every visual request can trigger online processing on the source, which can be slower and adds load on the on-prem system. In contrast, Import loads data into the Power BI data model, so visuals render from the in-memory engine (faster).

• Why that helps with the requirements:

• Why not A or B: Both rely on live data via DirectQuery, which contradicts the goal to minimize online processing and visuals performance.

• Why not D: It uses Import, but refreshing hourly adds unnecessary processing and complexity when daily refresh already satisfies currency needs.

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