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

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

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

• Accept: Acknowledging the risk without taking additional action.
• Transfer: Moving the risk’s financial impact to a third party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or employee training.
• Avoid: Eliminating the activity that creates the risk.

• Delete the City column
• Remove duplicates from the Country column

1. ???? City ??? ????? ?? ???? ?????? ???? ?????.
2. ???? ???? Country ?????? Remove duplicates ?????? ??? ?? ???? ??? ?????.

• Initial Intrusion: The compromised VPN account and stolen phishing credentials describe how the attacker first gained access, but that happened months earlier.
• Persistence: The scheduled tasks and recurring C2 connections show how the attacker maintained and automated continued access.
• Search and Exfiltration: This would involve locating and transferring data. The scenario does not primarily describe data discovery or theft.
• Cleanup: Cleanup involves removing evidence or covering tracks. Obfuscated scripts may make detection harder, but the main behavior here is maintaining access.

• A — Technical review by business owner: A business owner may approve the business impact, but a technical review is normally performed by technical personnel.
• C — Cost-benefit analysis after implementation: Cost-benefit analysis should occur before implementation to support the approval decision.
• D — Business continuity testing: This can be appropriate for major changes, but it is primarily part of business continuity and disaster recovery planning—not a universal change-management activity.

• ??????? ?? ??????? ????? ?? ???? Discount ????? ????? ??? 0.05.
• ?? Power Query Editor? ???? ???? Discount ?? ????:

• ???? ?????? 0.05.

• Remove Errors: ???? ?????? ???? ????? ??? ?????? ???? ????? ??? ???????? ??? ??????.
• Keep Errors: ????? ??? ??????? ???? ??? ?????? ???? ??? ???????.
• Edit the query in the Query Errors group: ???? ?? ???? ????????? ???????? ???? ?? ?????? ??? ????? ???? ???????? ???????.

• VLAN 10 for data
• VLAN 20 for voice

• A: Describes physical trunking or logical switch ports, not an SVI.
• B: An SVI can provide management access, but that is only one use—not the best description here.
• D: SVI use is not related to running out of physical ports.

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

• Controlar o fluxo de dados entre S3 e SageMaker;
• Aplicar regras de segurança por meio da VPC;
• Reduzir a exposição dos dados;
• Permitir acesso privado ao bucket do S3.

• Amazon Inspector: avalia vulnerabilidades, mas não gerencia o fluxo de dados.
• Amazon Macie: ajuda a descobrir e proteger dados sensíveis no S3, mas não cria a conexão com o SageMaker.
• S3 Glacier Deep Archive: é uma classe de armazenamento para arquivamento, não uma solução de conectividade.

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.

• The Speech resource subscription key
• The Azure region
• Optional endpoint and speech settings

python 
speech_config = speechsdk.SpeechConfig( 
    subscription=key, 
    region=region 
)

• SpeechSynthesizer converts text to speech.
• It uses a SpeechConfig, but it does not configure the service connection itself.

• AudioConfig: Defines audio input or output sources.
• AudioOutputConfig: Defines where synthesized audio should be sent.
• SpeechConfig: Configures the Azure Speech service connection.

• Review the risk register.
• Check the documented risk response strategy, such as using a backup resource, reallocating work, or adjusting sequencing.
• Implement the planned response promptly.

• B: Moving the task may affect the critical path and should not be done without first evaluating the planned response and impacts.
• C: Excluding a required task would change scope and business requirements without proper analysis or approval.
• D: Updating lessons learned and the risk log may be appropriate later, but it does not address the immediate problem. First, execute the response.

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

1. Clear principles and boundaries — Employees have freedom, but decisions must remain within clear organizational values, policies and limits.
2. High degree of freedom — Managers are trusted to make decisions rather than seeking continual approval from senior management.
3. Frontline customer responsibility — Customer-facing managers should be empowered to manage customer relationships and respond quickly to needs.
4. Transparent and ethical information — Information should be openly available and used honestly, supporting trust and informed decision-making.

• O dispositivo estar registado no Windows Autopilot;
• A atribuição de Profile1 ao grupo;
• O estado de associação ao Microsoft Entra ID e de inscrição no Intune/MDM.

• The message came from the claimed sender (authentication)
• The message was not altered (integrity)
• The sender cannot easily deny sending it (non-repudiation)

• Attackers can send unsigned phishing emails.
• Attackers may compromise a legitimate account and send signed malicious emails.
• Users may still be tricked by a validly signed message.

• A — Use a custom controller: An Apex class can contain the page’s logic.
• C — Use a standard controller with extensions: The standard controller provides basic CRUD behavior, while an extension adds custom logic.
• E — Use a standard controller: Useful when the page works mainly with one Salesforce object and needs standard functionality.

• A page with no controller for static or controller-free content.
• A custom controller with extensions; extensions are not limited only to standard controllers.

• Limiting the number of MAC addresses learned on a switch port
• Allowing only specific, approved MAC addresses
• Taking action when the limit is exceeded, such as dropping frames or disabling the port

• Smartphones and tablets
• Laptops and workstations
• Other mobile or endpoint computing devices

• Structure requirements documents
• Draft user stories and acceptance criteria
• Create templates for functional and nonfunctional requirements
• Turn natural-language descriptions into organized documentation or implementation examples

• A: “Automatically generating detailed requirements documents” overstates Copilot’s role; it assists but does not independently determine complete requirements.
• C: /help provides guidance about Copilot features, not reliable requirements-conflict detection.
• D: Stakeholder communication and meetings remain human responsibilities.

• Company documents
• Databases
• Knowledge bases
• Current web or business data

• A: Describes diversity and inclusive design, not grounding.
• B: Describes explainability or model interpretability.
• D: Describes documenting a model’s capabilities and limitations.

• Attack simulator — Used to run phishing and other attack simulations for user awareness training.
• Hunting — Used to proactively query security data and investigate potential threats.
• Incidents — Used to investigate and manage related alerts and active security events.

• 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

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

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.

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

• The job keeps 31 days of regular restore points. A backup from the week of January 1 is older than 31 days by March 20, so it is no longer expected to remain on the performance tier.
• It is also a weekly GFS full backup, retained for 14 weeks. Therefore, it is still protected and has not been deleted.
• In a Scale-out Backup Repository, older backups can be moved from the performance tier to the capacity tier—typically object storage—according to the configured offload policy.
• The archive tier is not selected because the question’s configuration does not indicate that the backup has been archived there.

• Scale out during the hours when customer traffic is high.
• Scale in during low-demand periods, reducing instance-hours and cost.
• Use scaling policies based on metrics such as CPU utilization or request count.

• Multiple Availability Zones: Improves availability and fault tolerance, but does not automatically reduce cost.
• Placement group: Helps with specialized performance or low-latency requirements, not cost optimization.
• Private subnets: Improve network security, but do not automatically adjust capacity or reduce EC2 usage costs.

• Normal or expected input
• Boundary values
• Invalid input
• Potential error conditions

• A is incorrect: it creates test code, not detailed test documentation.
• C is incorrect: it does not primarily integrate external testing frameworks.
• D is incorrect: executing tests requires your development environment or test runner.

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.

• Transport and handling
• Storage and warehousing
• Refrigeration
• Shelf-stacking or replenishment
• Other costs directly attributable to product P

• Information sources: Collect security-related data, such as network packets, system logs, audit records, or application events.
• Analysis: Examines the collected data to identify suspicious activity, attacks, or policy violations.
• Response: Takes or recommends action, such as generating alerts, logging the event, or supporting a protective response.

• RTO is how quickly service must be restored.
• RPO is how much data loss is acceptable.

• Snapshots: Restore points may be older and require restoration time.
• On-site backups: Usually require rebuilding or restoring systems, producing higher RTO/RPO.
• Journaling: Records database changes and can reduce data loss, but it still generally requires recovery or replay operations; it does not by itself provide the fastest service restoration.
• Hot site: Designed for rapid failover and minimal data loss.

• C — Before update
• D — Before insert

apex 
trigger AccountTrigger on Account (before insert, before update) { 
    for (Account acct : Trigger.new) { 
        acct.Description = 'Updated automatically'; 
    } 
}

• In after insert and after update, Trigger.new records are read-only.
• Use after triggers when you need the record’s final database Id or want to create/update related records.
• Attempting to change a field directly in an after trigger causes a read-only error.

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

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

• B — Both inner and outer classes can be declared as with sharing.

• C — Inner classes do not inherit sharing settings from the container class.

apex 
public with sharing class OuterClass { 
    public with sharing class InnerClass { 
        // Explicitly uses sharing rules 
    } 
}

• The audience and stakeholders
• The complexity and type of requirements
• The communication method and level of detail needed
• Whether to use diagrams, models, documents, demonstrations, or slides

• B: Authority to host the presentation is not the key preparation activity.
• C: Stakeholder sign-off may occur later; presenting requirements does not always require formal approval beforehand.
• D: A scribe may be useful in a meeting, but hiring one is not a core preparation requirement for presenting.

• Run the backup with WITH CHECKSUM
• Store the backup on an SMB network share

sql 
BACKUP DATABASE DB1 
TO DISK = '\\FileServer\SqlBackups\DB1_full.bak' 
WITH CHECKSUM;

• DMS does not create the SQL Server backups for you.
• You must provide a valid full database backup.
• You must continue taking transaction log backups while the source database remains online.
• The full backup and subsequent log backups must be available in the SMB share that DMS can access.
• WITH CHECKSUM enables backup checksum validation, helping detect backup corruption.

• File1 contains the evaluation configuration—for example, evaluators, test data, thresholds, or evaluation parameters.
• The GitHub Actions workflow must reference that file through the evaluation-config input so the action knows which evaluation to run.
• project-endpoint identifies the Microsoft Foundry project, but it does not identify the evaluation definition. It is also typically required, but it does not answer the specific requirement about using File1.

• Set credit quotas for an account or individual virtual warehouses.
• Define monitoring intervals.
• Trigger actions when usage reaches thresholds, such as sending notifications or suspending a warehouse.
• Help control unexpected warehouse spending.

• Account Usage: Provides historical usage and billing data; it does not enforce credit limits.
• Warehouse Limit Parameter: Not the Snowflake object used for account-wide credit controls.
• Credit Consumption Tracker: Not a standard Snowflake object.

• Determine the project budget — Budget development is a separate cost-management activity.
• Develop a communication plan — This belongs to project communications planning, not schedule completion.
• Establish baselines — Baselines are created after the schedule and related plans have been developed and approved. They formally capture the approved plan.

• The vulnerability scan identifies a vulnerability.
• The administrator verifies that the vulnerability is not present.
• Therefore, the scan produced a false positive.

• True positive: A vulnerability is reported and genuinely exists.
• False negative: A vulnerability exists, but the scan fails to detect it.
• True negative: No vulnerability exists, and the scan correctly reports no issue.

• Create the field in the CRM on the relevant person records—typically Lead and Contact in Salesforce.
• Give the Marketo Sync User read/write access to the field.

• Extracted text and images
• Page numbers and bounding polygons for citation or grounding
• Structured tables, including tables that continue across multiple pages
• Document structure such as sections and figures

• Document Extraction: Extracts basic text and images, but does not provide the full layout and structural metadata required here.
• Azure Content Understanding in Foundry Tools: A broader content-analysis service, not the single built-in Azure AI Search skill expected by this question.
• GenAI Prompt: Can transform or interpret content but does not inherently produce reliable document geometry and page-level polygons.

• Amazon S3 as the origin for static content
• Application Load Balancer (ALB) as the origin for dynamic content
• Amazon Route 53 configured to point the company’s domain name to CloudFront

• /static/* ? S3 origin; cache content at edge locations
• Dynamic paths such as /api/* ? ALB origin; forward requests to the EC2 application

• Distinct values = 69

• Unique values = 4

• Creating and training machine-learning models
• Testing and evaluating models
• Deploying models as usable endpoints