Test Prep CFA-Level-I Exam Prep
CFA® Level I Chartered Financial Analyst (Page 291 )

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

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

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

• How quickly the vendor must respond to incidents or requests
• Availability or uptime requirements
• Resolution time targets
• Performance expectations and penalties for failing to meet them

• SOW (Statement of Work): Describes the work, deliverables, scope, and schedule.
• MOA (Memorandum of Agreement): Documents an agreement in which parties commit to specific responsibilities.
• MOU (Memorandum of Understanding): Records a general intention to cooperate; it may not be legally binding.

• Red team: Offensive security; attempts exploitation and simulates attackers.
• Blue team: Defensive security; monitors, detects, and responds to attacks.
• Purple team: Combines red- and blue-team activities to improve defenses, but is not the best direct answer here.
• White team: Usually oversees or coordinates an exercise, including rules of engagement and scope.

• D — Value analysis: Correct. It examines an existing product to identify ways of reducing its cost while still providing the required functions, quality and reliability.
• E — Kaizen costing: Correct. It involves making continuous, small improvements and cost reductions while the product is already in production.

• Functional analysis: It is not limited to minimizing the cost of the originally defined functions. It examines what functions are required and how they can be provided at the lowest overall cost.
• Value engineering: Usually applies to the design and development of a new product, rather than being a fundamental redesign of existing organisational processes. That description is closer to business process re-engineering.
• Target costing: The target cost is generally established during the product development stage, before production begins. It is not continuously reset while the product is in production.

• Regression predicts continuous numeric outcomes, such as house price, temperature, or sales amount.
• Linear regression assumes the target can be estimated from a linear relationship between the input features and the target.
• In Azure Machine Learning, you use a labeled dataset containing:

• Classification predicts a category or class, such as “spam” or “not spam.”
• Clustering groups similar records without a known label; it is an unsupervised learning technique.

• CPU: Number of virtual CPUs and, where applicable, CPU reservations.
• Memory: Amount of memory and memory reservations.

• Network interface: Usually configured through the VM or workload networking configuration.
• PCI devices: Specialized hardware and not a standard VM Class resource in this context.
• Storage: Typically selected through storage policies or the VM’s storage configuration.

• Profitability and financial performance
• Long-term business viability
• Responsible use of resources
• Delivering returns to shareholders

• Social concerns people, communities, labour standards and human rights.
• Environmental concerns impacts on the planet, such as emissions and resource use.
• Legal is important for compliance, but it is not one of the three Triple Bottom Line pillars.

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

• Packet loss
• Latency
• Jitter
• Call quality by user, device, network, location, or building

• Teams Usage Report: Shows adoption and usage statistics, not detailed call-quality metrics.
• Teams Device Usage Report: Reports which devices are being used and how, but does not provide detailed packet-loss analysis.
• Microsoft Network Testing Companion: Helps assess network readiness before deployment, but it is not the primary tool for analyzing packet loss from actual Teams calls.

DAX 
Previous Year Sales = 
CALCULATE( 
    [Total Sales], 
    PARALLELPERIOD('DATE'[Month], -1, YEAR) 
)

• CALCULATE evaluates [Total Sales] after modifying the filter context.
• PARALLELPERIOD shifts the current date period. -1 moves it backward, and YEAR specifies a one-year shift.
• 'DATE'[Month] is the date column used for the time calculation. In a proper date table, this should be a real date column or an appropriate calendar column—not merely text such as "January".

• Bronze: Raw ingested data
• Silver: Cleaned, validated, and transformed data
• Gold: Business-level data for analytics, dashboards, and reporting

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

• Sustainability
• Performance efficiency
• Reliability

• Self-signed certificate: Causes a browser security warning, not incorrect name resolution.
• Nameserver record: A DNS problem would typically affect multiple users, not just one workstation.
• IP helper: Relays services such as DHCP across network segments; it does not resolve website names.

• Disabling a compromised account
• Blocking a malicious IP address
• Isolating an endpoint
• Creating or escalating an incident ticket

• Virus signatures: Primarily associated with antivirus or endpoint protection.
• Security agent deployment: Usually handled by endpoint-management or security-agent platforms.
• Vulnerability scanning: Typically performed by vulnerability-management tools.

• VPC: A logically isolated virtual network within a cloud provider; it describes network design, not the user-access model.
• NFV: Runs network services as software instead of on dedicated hardware.
• SaaS: Delivers software over the internet. Although the application may be delivered as SaaS, the question emphasizes its availability to multiple user groups, which points to multitenancy.

• Malware or malicious software
• Command-and-control tools
• Internet surveillance and intrusion software

• ITAR: A U.S. regulation controlling defense-related articles and services; it is not the international arrangement described.
• Palermo Convention: Focuses on transnational organized crime and related protocols, not export controls for cyber weapons.
• GDPR: European data-protection and privacy legislation.

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

• MTTC: Time required to contain or limit the incident’s impact — best match.
• MTTR: Time required to remediate or recover from the incident; this may include eradication, restoration, and cleanup, which goes beyond merely stopping spread.
• MTTD: How long it takes to discover the incident.
• MTBF: Average time between failures, generally a reliability metric.

• A — Tables
• B — Named file formats
• C — Schemas
• E — Databases

Why these are correct

• Tables: Can be cloned using CREATE TABLE ... CLONE. The clone initially uses zero-copy cloning, so storage is shared until changes are made.
• Named file formats: Can be cloned as database objects, preserving the file-format definition.
• Schemas: A schema and its eligible objects can be cloned.
• Databases: A database and its eligible schemas and objects can be cloned.

Why the others are incorrect

• Shares: A share is an account-level data-sharing object, not a normal cloneable database object.
• Users: Users are security principals and cannot be cloned with CLONE.

• Due diligence: Investigating and evaluating a third party before entering a business relationship.
• Attestation: An independent auditor’s examination and formal report—such as the SOC 2 report itself. The analyst is reviewing the attestation, not performing it.
• Internal audit: Examines the organization’s own processes and controls.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.

• Tracking who accessed or changed customer information
• Detecting unauthorized activity
• Supporting accountability and investigations
• Providing evidence for compliance and incident response

• Single sign-on not enabled: SSO improves convenience and centralized authentication, but it is not essential for access control.
• Complex passwords not required: This weakens authentication, but other controls may reduce the risk.
• Security baseline not consistently applied: A concern, but it is less specific and less immediately damaging than having no activity records at all.

• Security groups
• Dynamic security groups
• Cloud-only or synchronized security groups

• Microsoft 365 groups
• Distribution groups
• Mail-enabled distribution groups

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

• Honeypots: Decoy systems or services designed to attract attackers. Legitimate users should not access them, so activity there is a strong indicator of compromise.
• DNS sinkholes: Redirect malicious or suspicious DNS requests to a controlled destination. This can identify infected systems attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it is not an attacker-detection method.
• CI/CD: Automates software development, testing, and deployment.
• Threat modeling: Identifies potential threats and weaknesses before or during system design; it does not directly detect an active infiltrator.
• Data obfuscation: Makes information harder to understand, but does not identify attackers.

• Sales revenue is affected because internal sales are recorded at the transfer price.
• Operating profit is affected because revenue changes while costs may remain unchanged.
• Return on investment (ROI) is affected because ROI depends on operating profit and the division’s investment.
• Cost of components purchased is not affected by the transfer price. These are costs incurred when buying components from external suppliers, not the internal price charged for the division’s output.

• 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

• Understating expenses and liabilities
• Overstating profit
• Misleading users of the financial information
• Potentially breaching integrity, objectivity, and professional competence and due care

• 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

• Configure row-level security (RLS) using the sales region and the HR manager’s identity.
• Publish the reports and datasets through a Power BI app.
• Grant the HR managers permission to use the app, but do not add them as workspace members.
• App users can view and interact with reports while RLS limits them to their region.
• They cannot modify the report layout because they do not have workspace editing permissions.

• Adding them to the workspace gives them workspace permissions that may allow report or dataset changes, depending on the assigned role.
• Creating copies is unnecessary and creates maintenance and security problems.
• Hosting datasets and reports in different workspaces does not, by itself, provide the required controlled access.

• The users currently have Office 365 Enterprise E3 licenses assigned directly.
• Assigning Microsoft 365 Enterprise E5 through a group does not automatically remove their directly assigned E3 licenses.
• From the Licenses blade, you can select the E3 product and remove it from all assigned users in one operation. This requires less effort than editing 2,500 users individually.

• Identity Governance manages access reviews, entitlement management, and related governance—not bulk license removal.
• Set-AzureAdUser does not remove product licenses.
• Set-WindowsProductKey applies Windows product keys and is unrelated to Microsoft 365 licensing.

• A user connects with their Google account.
• Google associates the user’s SSH key with that identity.
• IAM roles determine whether they can log in.
• Access can be tied to a specific employee for auditing.
• Removing the IAM role removes their login access.

• compute.osLogin: regular OS login access
• compute.osAdminLogin: OS login with administrative privileges, typically including sudo

text 
enable-oslogin=TRUE

• Review administrative-role membership ? PIM access reviews
• Require justification for continued membership ? PIM can require justification when activating or maintaining privileged access
• Alerts about administrator assignment changes ? PIM alerts and notifications
• History of administrator activation ? PIM audit history
• See changes made to Azure resources ? PIM activation/audit information can be correlated with Azure Activity Logs

• Defender for Servers is the Defender for Cloud plan that protects Azure VMs and generates security alerts that can be reviewed in Defender for Cloud.
• Azure Diagnostics extension collects guest OS monitoring data, but it does not onboard VMs to Defender for Cloud or provide Defender security alerts.
• Data connectors are used for Sentinel integrations.
• Azure Storage Analytics and workflow automation do not provide VM protection.

• Who owns security risks and decisions
• Who is responsible for implementing controls
• Who reports security performance to management
• How security responsibilities align with business objectives

• B — Compliance with audit requirements: Governance may support compliance, but audit compliance is not its main objective.
• C — Monitoring security incidents: This is an operational security activity, not the central purpose of governance.
• D — Creation of tactical solutions: Governance establishes direction and oversight; tactical solutions belong to management and operational teams.

• On-premises resources, such as an existing database
• Cloud resources, such as Azure services or virtual machines
• Connectivity that allows the application to use both environments

• Public cloud: resources are entirely provided through a public cloud provider.
• Private cloud: resources are dedicated to one organization, typically on-premises or privately hosted.

• Maintain head office control: Transfer pricing generally supports decentralisation rather than direct head-office control.
• Establish centralised decision making: This conflicts with divisional autonomy.
• Develop a top-down culture: Transfer pricing is intended to support empowered divisions and goal congruence, not impose purely top-down management.

• The ERSPAN source is the device or interface whose traffic is being copied.
• The ERSPAN destination is the device receiving the encapsulated copy and forwarding it to the traffic analyzer.
• The local monitor session number is locally significant. Therefore, the source and destination do not need matching session IDs such as 47 or 48.
• The erspan-id identifies the ERSPAN stream and must correspond between the source and destination configuration.

• Identifies which user or department owns the device
• Supports inventory and compliance requirements
• Enables tracking of lost, stolen, retired, or unauthorized devices
• Helps enforce security controls such as mobile-device management and secure configuration

• Job compute isolates production pipelines from interactive development and terminates after the job completes.
• Autoscaling adds and removes workers during telemetry spikes, directly addressing bursty workloads.
• Photon can improve performance and reduce processing time, but it does not provide autoscaling, schema-drift handling, or exactly-once processing by itself.

• A — Shared compute: violates production isolation and can allow development workloads to affect ingestion.
• C — Larger fixed cluster: may improve capacity but cannot adapt efficiently to changing workloads.
• D — Disable autoscaling: directly conflicts with the requirement to handle telemetry spikes.

• Treatment one – easier to prepare: Convenience for the accounting team is not the main objective of financial reporting.
• Treatment two – fair representation: This is the correct choice because financial statements must faithfully represent the underlying transaction and its economic substance.
• Treatment three – maximises profit: Accounting policies must not be selected simply to manipulate or inflate reported profit.
• Treatment four – easier to understand: Understandability is important, but it cannot justify presenting information that is less faithfully represented.

• Microsoft Purview portal: Create and manage sensitivity labels and configure support for sensitivity labels used with Office files in SharePoint and OneDrive.
• SharePoint admin center: Primarily manages SharePoint settings. Older guidance and PowerShell procedures used SharePoint tenant configuration, which can make this question confusing.
• IRM: Concerns Information Rights Management and is a separate protection mechanism; it should not be used to identify the portal for configuring Microsoft Purview sensitivity labels.

• Box 1: No — The rule requires user.department to equal Engineering. Engineer does not match, so User1 is not in AU1. Admin1 cannot reset User1’s password.
• Box 2: No — Admin1’s role is scoped to AU1 and cannot manage users outside that AU.
• Box 3: Yes — Admin2 is a Global Administrator and can reset User3’s password.

• Lead investigator: Coordinates the investigation and directs the response.
• Information security representative: Provides security expertise and helps assess the incident.
• Technical representative: Preserves system evidence, takes forensic backups, and supports technical analysis.
• Legal representative: Advises on legal, regulatory, privacy, and evidence-handling requirements.

• Render thousands of animation frames
• Generate product images in multiple sizes
• Apply filters or transformations to a large image collection
• Produce visual effects for a video

• AWS Network Firewall can inspect and block traffic across a VPC when traffic is routed through the firewall. A Drop action rule can deny traffic from the suspicious source IP.
• GuardDuty findings are sent to Security Hub.
• A Lambda function can be invoked when Security Hub receives a new GuardDuty finding, extract the source IP, and update the Network Firewall policy with a blocking rule.

• GuardDuty threat lists: Used to identify or increase the severity of findings; they do not directly block VPC traffic.
• AWS WAF: Protects supported web applications, such as CloudFront or Application Load Balancers. It does not provide general VPC-wide traffic blocking.
• GuardDuty suppression rules: Suppress or hide findings. They do not block the suspicious traffic.

1. Open the Offenses tab

1. Open the offense details

1. Review contributing events

1. Analyze the attack chain

1. Investigate the assets

1. Validate and respond