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

• The message came from the claimed sender (authentication)
• The message was not altered in transit (integrity)
• The sender cannot easily deny having signed and sent it (non-repudiation)

• Compliance standards: May be a reason in some organizations, but it is not the primary security benefit.
• Increase delivery rates: Digital signatures do not generally improve email delivery.
• Block phishing attacks: Signatures can help recipients verify legitimate messages, but they do not block phishing by themselves.

• Matching hashes: The software likely has not changed.
• Different hashes: The software was modified or corrupted.

• Encryption: Protects confidentiality by making data unreadable; it does not primarily detect changes.
• Baselines: Define an approved system or configuration state, but they are not the specific integrity mechanism here.
• Tokenization: Replaces sensitive data with substitute values.

• Existing expected ROI: 15%
• New project ROI: 14%
• Cost of capital: 12%

• Project return = 14%
• Cost of capital = 12%
• It earns 2% more than the cost of capital, so it should increase shareholder value.

1. Create a temporary Onboarding OU.
2. Move the new account into it.
3. Move the restrictive SCPs from the organization root to the Production OU.
4. Allow the account to update AWS Config.
5. Move the account into Production after onboarding.

• An SCP attached at the organization root applies to every account and OU beneath it.
• An SCP attached to the Production OU applies only to accounts in that OU.
• Therefore, moving the restrictive SCP from the root to Production temporarily exempts the onboarding account without weakening the policies for existing production accounts.
• Once onboarding is complete, moving the account into Production subjects it to the normal restrictions.

Box 1: No

• configure_azure_monitor() configures Azure Monitor and the OpenTelemetry pipeline.
• LangChain requires its own instrumentation or callback tracer, such as AzureAIOpenTelemetryTracer.
• You must pass the tracer to the LangChain execution configuration so chains, tools, prompts, and model calls become spans in Application Insights.

Box 2: Yes

text 
OTEL_SERVICE_NAME=customer-agent 
OTEL_SERVICE_NAME=invoice-agent

• Where to find the TiMOS runtime image
• Which configuration file to load
• The IP address and related settings for the CPM management Ethernet port

• A: User authorization is configured in the router’s security configuration, not primarily in the BOF.
• C: Hardware initialization is performed by the boot process and system software.
• D: The system date and time are configured separately, often through NTP or CLI settings.

• A. Periodically rotate responsibilities: May reduce some risks, but it does not directly detect unauthorized changes.
• B. Review segregation-of-duties conflicts: Identifies incompatible access combinations, not whether a specific data change was unauthorized.
• C. Log changes in an outside application: Logs provide evidence, but someone must review and analyze them. Logging alone does not detect misuse.
• D. Independent review: Directly detects unauthorized changes and reduces the risk that the person making the change can conceal it.

• Deterrent control: The signs warning that people may be filmed can discourage unauthorized activity. They do not physically prevent the activity, but they may influence behavior.
• Detective control: CCTV detects or records activity so security personnel can identify incidents and investigate them later.

• Preventive: Stops an incident from occurring, such as a locked door.
• Corrective: Restores systems after an incident, such as backups.
• Directive: Instructs people what to do, such as security policies or warning instructions.
• Compensating: Provides an alternative control when the preferred control cannot be used.

• GPS coordinates
• Date and time the image was taken
• Camera or device information
• Image dimensions and software used

• Log data: Records generated by systems or applications, not normally embedded in image files.
• Encrypted data: Information intentionally encoded to prevent unauthorized access.
• Sensitive data: A broad classification, not the specific type of information being extracted.

1. Install a Cassandra-compatible ODBC driver.
2. Configure a data source name (DSN), if required.
3. In Power BI Desktop, select Get Data > ODBC.
4. Choose the configured DSN and connect.

• Microsoft SQL Server database: Connects to SQL Server, not Cassandra.
• OLE DB: Requires a compatible OLE DB provider; this is not the standard choice for Cassandra in Power BI.
• OData: Requires Cassandra data to be exposed through an OData service, which is not the normal direct connection method.

• Allow only approved MAC addresses
• Limit the number of learned addresses
• Shut down or restrict a port when a violation occurs

• Load balancer: Distributes application traffic; it does not protect switch MAC tables.
• IPS: May detect some attack traffic, but it is not the direct control for limiting MAC addresses on switch ports.
• NGFW: Filters routed network traffic, while this attack targets Layer 2 switch behavior.

• The load balancer provides the listener’s frontend IP address.
• The active SQL Server node must also respond to that same listener IP.
• Enabling Floating IP allows the listener IP to be preserved and handled correctly by the active replica.
• Without it, SQL connections may be sent to a node that cannot correctly claim the listener address.

• A health probe for the SQL Server port
• A load-balancing rule using the listener port
• Floating IP enabled on that rule

• IDS attack signatures: Primarily detects suspicious network activity; it is not the best control for scanning uploaded documents.
• Load balancer: Distributes traffic and can improve availability, but does not inspect files for malware.
• WAF: Helps block web attacks such as command injection and SQL injection, but it is not primarily a malware-scanning solution.

• Penalty clauses (3): Set a financial consequence when the supplier fails to meet agreed performance standards. In commercial contracts, these must be drafted carefully because unenforceable penalties may be challenged; liquidated damages are often preferred.
• Service credits (4): Reduce the amount payable, or provide a credit, when the supplier misses SLA targets. They are a common remedy for service underperformance.

• Warranties (1): Usually provide assurances about quality, condition, or compliance, but they are not the normal direct remedy for missing ongoing SLA targets.
• Force majeure clauses (2): Excuse or protect a supplier from liability when exceptional events outside its control prevent performance. They do not compensate the buyer for ordinary poor performance.

• Process Builder: Automates actions based on record changes but does not create interactive forms.
• Approval Process: Routes records for approval; it is not designed to collect information through a wizard.
• Outbound Message: Sends information to an external system; it does not provide a user interface.

• Insert is used when you are creating a new record. It saves the record to the table and then leaves the form.
• Update is used when editing an existing record. It saves the modifications and then leaves the form.

• Authentication: Verifies who the user is.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records activity such as login times and resource usage.

• CIA: Confidentiality, integrity, and availability—the three core security goals.
• ACL: Access Control List, which defines permitted or denied traffic or access.
• PEM: A certificate and key encoding format, not the primary function of RADIUS.

• S3 Glacier Deep Archive is designed for long-term archival data with very infrequent access and has a lower storage cost than S3 One Zone-IA.
• The documents are copies stored elsewhere, so reduced availability and delayed retrieval are acceptable.
• An S3 interface VPC endpoint allows private access from the VPC without exposing the bucket through the public internet.
• A bucket policy can restrict access to requests coming through that endpoint.

• Explain questions from the exam page
• Check whether the stated answer is technically correct
• Compare answer choices and eliminate distractors
• Clarify Azure AI concepts and terminology
• Point out when an answer key appears unreliable or when an image is missing

• New Cat 5 line: Useful if testing shows a damaged cable, but the issue is specifically triggered when the fax is active.
• 802.1Q tagging: Used to carry multiple VLANs across trunk links; it does not solve the issue by itself.
• Change the MTU: Relevant to packet-size or fragmentation problems, not typical fax-related interference.

• B — Sales staff will tender for riskier contracts:

• C — Sales staff will encroach on other territories:

• D — Sales staff will look for new jobs:

• Containment policy: controls permitted communication during containment.
• Detection/response configuration: determines when containment is initiated.

• Customer needs: Primary focus in agile; guides prioritization and decision-making.
• Organization’s needs: Important constraints, but processes should be tailored when they create waste.
• Agile lead/project manager: Their role is to facilitate value delivery, not prioritize their own preferences.

• Injection
• Broken access control
• Authentication failures
• Security misconfiguration
• Cross-site scripting

• STIX: A standardized language and format for exchanging threat intelligence.
• OVAL: Used to describe and assess system vulnerabilities and configuration issues.
• Threat intelligence feed: Provides current indicators and intelligence about threats, but not necessarily a structured overview of common application exploitation methods.
• CVE: A catalog of individually identified, publicly disclosed vulnerabilities.

1. Yes — Microsoft Foundry provides a secure, governed environment for building and managing generative AI applications and agents. It brings together models, data, tools, evaluation, deployment, and monitoring.

1. Yes — Foundry is designed for enterprise workloads and supports scaling AI applications as usage grows. Scalability comes from the underlying Azure services and managed infrastructure.

1. Yes — Foundry can be used in solutions involving image recognition and computer vision. Applications can use vision-capable models and Azure AI vision capabilities for tasks such as image analysis, object detection, and OCR.

• A — Increased call deflection: o KCS disponibiliza conhecimento reutilizável para clientes e agentes, ajudando a resolver dúvidas sem abrir ou continuar chamadas.
• C — Reduced issue resolution time: os representantes reutilizam artigos e soluções já documentadas, acelerando o atendimento.
• E — Optimized use of resources: o conhecimento compartilhado reduz retrabalho e melhora o uso dos recursos da equipe.

• On VirtualNetworkA: enable Allow gateway transit.
• On VirtualNetworkB: enable Use remote gateways.

• Escape to host: A virtualization attack where code escapes a guest VM and accesses the host system. Nothing in the scenario mentions virtualization.
• Browser extension: Can redirect or manipulate web-browser traffic, but not normally database-server traffic.
• Valid accounts: Describes using stolen or compromised credentials, not redirecting network traffic.
• Process injection: Injecting malicious code into a legitimate database or networking process could allow an attacker to alter how that process handles outgoing traffic.

• The listener uses a virtual IP address shared by the availability-group replicas.
• Floating IP, also called Direct Server Return (DSR), allows the SQL Server nodes to respond using the listener’s IP address rather than their individual VM IP addresses.
• This is required for the availability-group listener to function correctly with an Azure internal load balancer.

• A single summarized value, such as total annual sales
• Progress toward a defined target or goal
• Whether performance is below, near, or above the target

• Table: Displays detailed records or summarized rows, but not goal progress visually.
• Stacked Bar: Compares multiple categories and their parts.
• Donut: Shows how a total is divided among categories, not progress toward a target.

• The backup file is complete and uncorrupted.
• The required data can actually be recovered.
• The recovery process and documentation work as expected.
• Recovery objectives, such as acceptable downtime, can be met.

• Backup logs may show that a job completed, but not that the backup is usable.
• File size does not prove the contents are valid.
• Email notifications may confirm process completion, not recoverability.
• Appointing a DBA does not itself validate backups.

• Reporting relationships
• Organizational structures
• Leadership styles
• Team maturity
• Individual and group behavior
• Communication and motivation

• Acquire Project Team: Focuses on obtaining the people needed for the project.
• Develop Project Team: Focuses on improving team skills, relationships, and performance.
• Manage Project Team: Focuses on tracking performance, resolving issues, and managing changes within the team.

1. Open Notepad as Administrator.
2. Open:

1. Remove or correct the line mapping the website to the wrong IP address.
2. Save the file.
3. Optionally run:

cmd 
   ipconfig /flushdns

• Honeypots are deliberately vulnerable or attractive systems designed to lure attackers. Legitimate users should not normally access them, so activity there can indicate a successful intrusion or lateral movement.

• A DNS sinkhole redirects requests for known malicious domains to a controlled internal system instead of the real destination. Security teams can monitor those requests and identify compromised devices attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it is a protection method, not an attacker-detection method.
• CI/CD: Automates software development and deployment processes.
• Threat modeling: Identifies potential threats during design and planning.
• Data obfuscation: Makes information harder to understand, but does not directly detect infiltrators.

• A — VARIANT "null" values are not the same as SQL NULL values: True

• B — Frequent, single-row DMLs: False

• C — Validate data before loading into the target table: True

• D — Use staging tables to manage MERGE statements: True

• Security
• Availability
• Processing integrity
• Confidentiality
• Privacy

• Whether controls are suitably designed, and
• Whether they operated effectively over a period of time

• User2 is in Group1, so CA2 applies.
• CA2 targets Office 365.
• CA2 requires MFA OR an app protection policy.
• User2 has no app protection policy, but if User2 successfully completes MFA, the OR condition is satisfied.
• The device being noncompliant does not matter because CA2 does not require device compliance.
• CA1 applies only to Global Administrators. Unless User2 is also a Global Administrator, CA1 does not apply.

• Response and resolution time frames
• Availability or uptime requirements
• Performance targets
• Support obligations
• Penalties for failing to meet requirements

• SOW (Statement of Work): Defines the project’s scope, tasks, and deliverables.
• MOA (Memorandum of Agreement): Describes cooperation and responsibilities between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, usually without detailed enforceable service targets.

• Accept: Acknowledge the risk without taking additional action.
• Transfer: Shift the risk’s impact to another party, such as through insurance or outsourcing.
• Mitigate: Reduce the likelihood or impact, such as by implementing controls.
• Avoid: Eliminate the activity or situation that creates the risk.

• Feedback form: Captures opinions, not necessarily actual behavior; users may not respond.
• Questionnaire: Relies on memory and subjective judgments about usefulness.
• Interviews: Can provide valuable qualitative insights, but a sample of users may not represent overall usage accurately.

• A is incorrect: Flow Debugger is for debugging Salesforce Flows, not Trust Layer masking.
• B is incomplete/misleading: Requesting audit data may be part of reviewing the results, but collection and storage must first be enabled.
• C is correct: It describes the initial validation step.

• Third-party attestation: Provides independent validation, but is typically periodic and performed by an external party.
• Penetration testing: Simulates attacks to identify exploitable vulnerabilities; it does not primarily track compliance.
• Vulnerability scans: Identify technical weaknesses, but do not provide a detailed review of procedures or compliance activities.

1. Wireless AP

1. Router

1. Firewall

1. Device placement

• 24 cores: Available in the Business Critical provisioned-compute configurations.
• Approximately 124 GB memory: Matches the memory capacity of the relevant Business Critical hardware configuration.
• More than 50,000 IOPS: Business Critical uses local SSD storage and provides the high I/O performance required here.
• 500 GB storage: Well within the tier’s supported capacity.

• Premium: The DTU-based Premium tier does not provide the required combination of compute, memory, and I/O characteristics.
• Hyperscale: Hyperscale is primarily intended for very large databases and independent storage scaling. It is not the best match for these specific high-memory and high-IOPS requirements.

• Red team: Offensive security; simulates attackers and validates exploitability.
• Blue team: Defensive security; monitors, detects, and responds to attacks.
• Purple team: Helps red and blue teams collaborate and improve defenses; not usually the primary testing role.
• White team: Oversees and coordinates the rules, scope, and authorization of an exercise.

• Streams — track change data for tables or views.
• External tables — reference data stored in an external cloud storage location.

• Role — account-level security object.
• Warehouse — account-level compute resource.
• User — account-level security object.
• Share — account-level object used to share data.

• Floating IP must be enabled on the load-balancing rule.
• Session persistence should normally remain None.
• The health probe determines which replica should receive traffic.
• Client-IP persistence is unnecessary and can cause connections from the same client to remain associated with a backend replica longer than intended.

• Q9 — Client IP session persistence: No
• Q10 — Floating IP: Yes

• The Intune device limit restriction does not apply in the normal way; DEM enrollment supports up to 1,000 devices.
• However, the Microsoft Entra maximum number of devices per user setting can still impose a limit when the enrollment creates an Entra device object.
• Therefore, a DEM account is not automatically unlimited. The effective limit depends on the Entra device setting and the enrollment/join type.