CFA CFA I Exam Prep
CFA Level I Chartered Financial Analyst (Page 326 )

• Crowd-sourced evaluation: Requires recruiting and managing many evaluators.
• Human-worker evaluation: Provides human judgment but requires coordination, labeling instructions, and quality control.
• RLHF: Is a training and alignment process, not simply a low-overhead model comparison method.
• Automatic model evaluation: Quickly evaluates outputs using predefined toxicity or quality metrics with minimal manual effort.

• 25 – Traditional SMTP server-to-server mail transfer; often blocked for client submission and not inherently secure.
• 110 – POP3 for receiving email; unencrypted by default.
• 143 – IMAP for accessing email; unencrypted by default.
• 587 – Authenticated email submission and commonly secured with TLS.

• 10.2.1.0 — network address
• 10.2.1.1 — usable host
• 10.2.1.2 — usable host
• 10.2.1.3 — broadcast address

• A PostToolUse hook for file writes under src/api/ that runs the linter.
• A separate PostToolUse hook for API/data processing that normalizes payloads to snake_case.

• Compute: Not used; no virtual warehouse is required.
• Data Storage: Not scanned again.
• Metadata: May help Snowflake manage and validate cached results, but it is not the Snowflake architectural layer identified as serving the request.
• Cloud Services: Handles query coordination, metadata services, authentication, and result-cache access.

• Data source: Folder
• Transformation: Remove the Content column (or keep only the file-metadata columns)

Why

• File name
• Extension
• Date modified
• Folder path
• Content — the binary contents of the file

• Driver node: Coordinates Spark jobs and runs in the compute environment.
• Worker node: Executes tasks and processes data.
• Databricks Filesystem (DBFS): Provides storage access for data used by compute resources.

• Least privilege: Limits users to only the access necessary for their job.
• Background checks: Help identify potentially risky individuals before employment.
• Separation of duties: Ensures that one person cannot complete a sensitive process alone, reducing fraud and abuse.

1. Wireless AP

1. Router

1. Firewall

1. Device placement

• # Development
• # Testing
• # Production

• Separate endpoints: relate to compute or connectivity, not dashboard labels.
• Separate queries: retrieve or transform data but do not designate visual sections.
• Direct text written into the dashboard in editing mode: dashboards use text boxes, typically with Markdown formatting, rather than arbitrary text placed directly on the canvas.

• A: Knowledge of IT platforms, networks, and methodologies — Useful technical knowledge, but the CISO does not need to be the deepest technical expert.
• C: Regulatory and project management knowledge — Important, but compliance and projects must still support the organization’s broader needs.
• D: Managing people and resources — Essential for execution, but effective management of the wrong security priorities will not produce good results.

• sn_si_admin is an SIR administrator role.
• The prefix helps prevent naming conflicts between applications.
• It does not refer to a “Secure Identity token” or an instance security check.

• A — If there is no demand, there should be no production.

• B — Not all sales equal profit.

• C — Stocking up on inventory is bad for business.

• D — All costs, except materials, are considered fixed.

• E — Departments should operate at full capacity regardless of bottlenecks.

• Deterrent control: The signs warning people they may be filmed discourage unauthorized or malicious behavior. They may prevent incidents by influencing behavior, but their primary purpose is to deter.
• Detective control: The CCTV system monitors and records activity so security personnel can identify suspicious or unauthorized actions.

• Preventive: Blocks or prevents an incident, such as a lock or access-control system.
• Corrective: Fixes or restores systems after an incident.
• Directive: Tells people what they must do, typically through policies or procedures.
• Compensating: Provides an alternative control when the preferred control cannot be used.

• Custom domains are supported.
• It provides dedicated compute instances.
• It offers enough storage for the applications.
• It supports multiple instances with load balancing between them.
• It is less expensive than higher tiers such as Premium.

• Free and Shared use shared compute and have limited storage, so they cannot meet the dedicated-instance requirement.
• Basic provides dedicated compute and custom domains, but the question’s requirement for the broader multi-instance/load-balancing capability is intended to point to Standard.

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

• File policy in Microsoft Defender for Cloud Apps: Can detect activity involving files, but it is not designed specifically to investigate risk from departing or deleted users.
• Access review policy in Microsoft Entra: Reviews whether users should retain access to resources; it does not detect historical document downloads.
• Alert policy in Microsoft Defender for Office 365: Primarily handles alerts for email and collaboration threats, not insider-risk investigations involving departed users.

• Root path cost
• Port priority
• Port ID

text 
interface GigabitEthernet0/1 
 spanning-tree vlan 10 port-priority 64

• Interface number: Helps form the port ID but is not normally configured as the preference value.
• VLAN priority: Not used to select a preferred forwarding interface.
• Hello time: Controls how often BPDUs are sent; it does not select a preferred port.

• Matching hashes: The software is likely unchanged.
• Different hashes: The software or its contents have been modified.

• Encryption: Protects confidentiality, not primarily integrity.
• Baselines: Document expected configurations and support comparison, but hashing is more directly suited to verifying file integrity.
• Tokenization: Replaces sensitive data with tokens and is unrelated to software tampering.

• nmap - 10.11.1.130 — a network scanning command; mitigated with controls such as firewalls, monitoring, or access restrictions.
• “Click this link to get your free gift card.” — a phishing or social-engineering message; addressed through user awareness, email filtering, and authentication controls.
• “Your connection is not private.” — indicates a certificate or TLS validation problem; addressed by correcting the certificate or secure-connection configuration.

apex 
for (Account updatedAccount : Trigger.new) { 
    AccountTriggerHelper.notinyxternalSystem(updatedAccount.Id); 
}

• Too many callouts: The callout occurs asynchronously in the future method, and each future transaction can perform its permitted callouts.
• Too many SOQL queries: The SOQL query is inside the future execution, not repeatedly in the trigger transaction.
• Callout from triggers not supported: Direct callouts from triggers are prohibited, but the trigger delegates the callout to asynchronous Apex, which is the correct pattern.

• AB’s own PPE: $100m
• CD’s PPE in its individual accounts: $50m
• Fair value uplift at acquisition: $40m
• Remaining useful life: 10 years
• Extra depreciation each year: $40m ÷ 10 = $4m
• Four years’ extra depreciation to 31 December 20X4: 4 × $4m = $16m
• Remaining fair value uplift: $40m - $16m = $24m

• A is valid:

apex 
  for (Account theAccount : AccountList) { 
      // process theAccount 
  }

• D is conceptually valid, using an index:

apex 
  for (Integer i = 0; i < AccountList.size(); i++) { 
      Account theAccount = AccountList[i]; 
  }

• B is invalid because for(AccountList) is not valid loop syntax.
• C is invalid because each item is an Account, not a List.

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

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

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

• Accept: Acknowledge the risk and take no additional action.
• Mitigate: Reduce the likelihood or impact of the risk through controls.
• Avoid: Eliminate the activity or situation causing the risk.
• Transfer: Shift responsibility or financial impact to another party, such as through insurance or a contract.

Correct reasoning

• Create storage5 as a General-purpose v2 (StorageV2) account.
• Configure Blob object replication from storage5 to an existing compatible storage account.
• The destination must support object replication—typically another StorageV2 or premium block blob account.
• Blob versioning must be enabled on both accounts.
• Blob change feed must be enabled on the source account.
• The accounts must meet Azure’s object-replication requirements, including being in supported regions and having compatible configuration.

• Two-part tariff pricing: $10 per unit
• Dual pricing: $20 per unit

Two-part tariff pricing

Dual pricing

• Division X, the seller, is credited with the market price: \(\$20\)
• Division Y, the buyer, is charged the marginal cost: \(\$10\)

• Key-based authentication: Provides an endpoint secured with API keys.
• Real-time REST access: Supports online inference through an HTTP/REST endpoint.
• No VM vCPU quota consumption: Microsoft hosts and manages the underlying infrastructure, so your subscription’s VM quota isn’t used.

• Batch: Intended for asynchronous, large-volume processing rather than real-time requests.
• Self-hosted container: You manage the infrastructure and typically need compute resources and quota.
• Standard: This is not the clearest deployment type for the stated requirements; the specific Foundry option is serverless API.

• SOSL searches text across objects and is not appropriate for selecting Account table columns.
• describeSObjects() provides metadata about objects and fields, but it does not itself build or execute the query.
• Dynamic Schema binding supports runtime determination of object and field information, which is required here.
• REST API is unnecessary because this is being implemented in Apex.

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.

• Endpoint Manager: manages hosts and sensor-related settings.
• Falcon Investigator: supports investigation and analysis, but does not necessarily grant RTR access.
• Remediation Manager: handles remediation-related actions rather than interactive host access.

• A. IDS attack signatures: An IDS primarily detects suspicious network activity; it is not the best tool for scanning uploaded files.
• C. Load balancer: Improves availability and distributes traffic but does not inspect files for malware.
• D. WAF: Protects web applications against attacks such as SQL injection and command injection. It may inspect HTTP requests, but malware scanning of uploaded PDFs is the key requirement here.

• Third-party enterprise application with embedded AI: The provider manages most security controls. The customer mainly manages users, data, and configuration.
• Application using an existing third-party FM: The customer controls the application and its inputs/outputs, but the provider controls the underlying model and infrastructure.
• Fine-tuning a third-party FM: The customer has additional responsibility for training data, data protection, and model behavior, but still depends on the provider’s base model and platform.
• Building and training a model from scratch: The customer controls the model, training data, application, deployment, and many security safeguards. This creates the greatest security ownership.

• Static IP address: Not needed if the workstation already has network connectivity.
• Subnet mask: Incorrect subnetting would usually prevent local communication, including pinging the server.
• Default gateway: Primarily affects communication outside the local network; it does not normally prevent finding an internal domain controller.

• NAT traversal: Helps WAN Edge, vSmart, and vManage devices discover how to reach one another through NAT.
• Initial orchestration: Authenticates and introduces devices when they first join the SD-WAN fabric.
• Connection brokering: Provides information that allows devices to form their required control connections, after which the vBond is generally not in the data path.

• WAN Edge: Forwards user traffic and forms secure tunnels.
• vSmart: Controls the overlay control plane and distributes routes and policies.
• vManage: Provides centralized management, configuration, and monitoring.

• The team should inspect its way of working during retrospectives.
• The team can identify root causes of delays and agree on process improvements.
• The leader facilitates the removal of impediments and provides support, but does not impose solutions.

• A: An impediment log can help track issues, but documentation alone does not resolve them.
• B: Directing the team toward solutions conflicts with agile empowerment and self-management.
• C: Adding impediments to the product backlog may incorrectly treat team problems as product features and delay resolution.

• miami.weyland.com requires a custom domain, which is not available in the Free tier.
• Two instances require a tier that supports scaling out. Standard supports multiple instances.
• SSL support is available in Standard.
• 12 GB of storage exceeds the storage limit of the Basic tier in the older Azure pricing model used by this question.
• Standard provides sufficient storage and features while being cheaper than higher tiers—though higher tiers are not listed here.

• Free/Shared: insufficient features for custom domains, SSL, and multiple instances.
• Basic: supports some production features, but its storage capacity is insufficient for the required 12 GB.

• To identify the number of errors: select Column quality. It shows the percentage and count of Valid, Error, and Empty values for each column.
• To resolve errors: use the appropriate error transformation:

• Repetitive and time-consuming
• Based on measurable conditions, such as last check-in time
• Easy to automate with alerts, dashboards, or scheduled reports
• Important for ensuring scan coverage

• Assigning custom recommendations usually requires analyst judgment and context.
• Analyzing false positives can sometimes be assisted by automation, but validation often requires human review.
• Rendering an additional executive report increases reporting activity rather than reducing a core operational workload.

Why this is correct

• Each user authenticates with their own Google account.
• Google manages the user’s SSH key association.
• IAM controls who can access instances.
• Access can be audited by user identity, so security can determine who accessed a VM.
• Granting the role to a Google group avoids managing permissions individually.

Why the others don’t apply

• A: A shared private key is difficult to distribute securely and cannot reliably identify which employee used it.
• B: Manually collecting and deploying keys on every instance is operationally inefficient and complicates auditing.
• D: A project-wide shared key has the same identity and key-management problems as option A. It also does not provide per-user accountability.

• Create a CodeCommit repository in the secondary Region.
• Use CodeBuild to run a Git mirror operation from the primary repository to the secondary repository.
• Use EventBridge to detect relevant repository events, such as a pull request being merged.
• Invoke a Lambda function, which starts the CodeBuild project.

• B: Amazon S3 is object storage, not a Git repository that developers can use as a CodeCommit remote.
• C: CodeArtifact is intended for packages and artifacts, not source-code repository mirroring.
• D: An AWS Cloud9 environment is not an appropriate automated replication mechanism and would require manual or persistent infrastructure management.

• Security controls
• Processes and procedures
• Compliance evidence
• Performance against contractual requirements

• Service-level agreement (SLA): Defines expected service performance, such as uptime and response times.
• Memorandum of agreement (MOA): Documents a general agreement between parties, but does not necessarily provide audit rights.
• Supply chain analysis: Identifies risks across suppliers and dependencies, but is not a contractual mechanism for reviewing vendor controls.

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

• terraform init is normally required first, especially for a new or changed working directory. It installs providers/modules and configures the backend.
• terraform plan previews the proposed changes.
• terraform apply applies those changes. It also creates a plan internally if you have not supplied a saved plan.

text 
terraform init 
terraform validate       # optional but recommended 
terraform plan 
terraform apply

• Amazon EC2 instances — ???????? ?? ?? ??????? CPU, memory ??? instance size ???????? ???????
• AWS Lambda functions — memory configuration ?????????? ???????
• Amazon EBS volumes — volume type ?? size optimize ???? ???????
• ??????? ECS workloads — resource configuration ? cost optimization-?? ???????

• Memory ? compute usage ?????????? ???? custom code ????? ???? development ? maintenance ??????
• Cost allocation tags ???? ????? ??? ?????? ???? ??????? ???; inefficient resource ??????? ?? recommendation ???? ???
• CloudTrail resource ???? ?? API activity ??????, resource utilization ????

• Existing Eventhouse data: remains available only in the KQL database.
• Data ingested after enabling the feature: is copied to OneLake and can be accessed through OneLake file explorer.
• New databases: are irrelevant; the setting applies to the selected KQL database.

• QuickVisualize is used to create and render a Power BI report from a DataFrame.
• The typical pattern is:

python 
PBI_visualize = QuickVisualize( 
    get_dataset_config(df), 
    auth=device_auth 
) 


PBI_visualize

• get_dataset_config(df) prepares the dataset configuration.
• auth=device_auth supplies authentication for the Power BI connection.
• Evaluating PBI_visualize renders the report in the notebook.

• Box 1: No
• Box 2: Yes
• Box 3: Yes

• Espionage: Stealing information, usually for competitive or political purposes.
• Data exfiltration: Unauthorized removal or transfer of data.
• Nation-state attack: An attack sponsored or conducted by a government.
• Shadow IT: Unapproved technology or access methods used by employees.

• Data owners: Decide who should have access and approve the access rules.
• Business process owners: May help define business requirements, but normally do not enforce technical permissions.
• Security steering committee: Provides governance and direction; it does not manage individual access rights.
• Security administrators: Apply and enforce the approved access controls.