Test Prep LSAT Test Exam Prep
Law School Admission Test: Logical Reasoning, Reading Comprehension, Analytical Reasoning (Page 102 )

• 50% memory utilization baseline: The environment can be provisioned with excess capacity, leaving room for growth and workload spikes.
• Storage scalability: Cloud storage can generally be expanded as needed without redesigning the physical platform.
• Single circuit failure resilience: A properly designed IaaS provider uses redundant power circuits and infrastructure, so failure of one circuit should not take the platform offline.

• A — Dual PDUs: Helps with power redundancy but does not provide storage scalability.
• C — Network load balancing: Provides network-path resilience, not memory or storage scalability, and does not address a power-circuit failure.
• D — Multiple NAS devices: May improve storage capacity, but does not inherently provide power resilience or the required compute-capacity baseline.

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

• Namespace: The namespace associated with the code where the checkpoint was set.
• Time: When the checkpoint was captured or executed.

• Exception: Exceptions are viewed through debug logs or execution results, not as the primary Checkpoints tab information.
• Debug Statement: System.debug() output belongs in the Logs tab. A checkpoint captures program state, such as variables and their values, at a specific point in execution.

• The server accepts unauthenticated image uploads, which creates an opportunity for an attacker to upload a malicious script disguised as an image or using an unexpected file type.
• A web shell is a malicious script placed on a web server that gives an attacker remote command execution through web requests.
• The suspicious process and outbound connection to a low-reputation IP are consistent with the attacker using the web shell to execute commands or establish communication with command-and-control infrastructure.

• Worm: Usually self-propagates across multiple systems; the scenario focuses on the upload page.
• Cryptocurrency mining: Possible, but there is no indication of resource-intensive mining activity or insider involvement.
• Rootkit Trojan over RDP: The evidence points to the vulnerable upload functionality, not an exposed RDP service.

• Design Studio > Emails ? create an email-template folder
• Design Studio > Landing Pages ? create a landing-page-template folder
• Add the relevant assets to each folder
• Right-click the folder and choose Share Folder
• Select the destination workspaces

• Shared capacity

• Fabric capacity — F SKUs

• Fabric trial capacity

• Existing Power BI Premium — P SKUs

• A. IDS attack signatures: An IDS primarily detects suspicious network activity; it is not the best control for scanning uploaded documents for malware.
• C. Load balancer: Distributes traffic among servers and improves availability, but does not inspect files for malware.
• D. WAF: Protects web applications against attacks such as SQL injection and command injection. It may help secure the upload function, but malware scanning is the key requirement here.

• B. Versioned configuration files — Infrastructure is defined in machine-readable files and tracked in version control, allowing repeatable provisioning and change history.
• D. Docker files — Assuming “Doctor files” is a typo for Dockerfiles, a Dockerfile declaratively defines how to build a container image and is commonly considered infrastructure/configuration as code.

• A. Cloned virtual machine images — These are prebuilt infrastructure artifacts, but cloning an image is not itself a code-based infrastructure definition.
• C. Change management database records — A CMDB records information about infrastructure; it does not define or provision that infrastructure.

• Each team’s Bedrock workflow uses a separate IAM service role.
• The role’s Amazon S3 permissions can be limited to only that team’s customer folder or objects.
• This enforces least privilege and prevents one team’s Bedrock application from accessing another team’s data.
• Access is enforced by AWS permissions, not by asking users to provide a customer name in each request.

• A single role with broad S3 access does not provide team-level isolation.
• Asking teams to specify a customer name is not an access-control mechanism.
• Redacting data does not prevent unauthorized access.
• A bucket policy alone is insufficient unless it explicitly enforces the required team-role restrictions.

• 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

• Reduce the training data: Usually makes overfitting worse.
• Add hyperparameters: Hyperparameters already control training; simply adding them does not solve the problem. Proper tuning could help, but that is not what the option states.
• Increase training time: More training can worsen overfitting if the model is already memorizing the training data.

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

Step 1: Calculate the rights issue price

Step 2: Calculate the number of new shares

Step 3: Calculate the value after the issue and project

• Rights issue proceeds: $21.6m
• Project NPV: $5m

Step 4: Calculate the theoretical ex-rights price

• Firewalls and routers
• Servers and applications
• Endpoint devices
• Authentication systems
• Cloud services

• Centralized log collection
• Event correlation
• Dashboards and reporting
• Alerting
• Compliance support

• Due diligence: Researching and evaluating a third party before entering or continuing a business relationship.
• Internal audit: Evaluates controls within the organization itself.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.
• Attestation: A formal statement or report—such as a SOC 2 report—provided by an independent party about an organization’s controls.

• Fine-tuning requires a properly formatted training dataset.
• For classification or instruction-style fine-tuning, examples are supplied in JSONL format.
• Each line represents one training example, typically containing the input prompt and the desired completion or label.
• The file must then be uploaded or made available to the Microsoft Foundry fine-tuning workflow.

• A: Prompt Flow is useful for prompt experimentation, but it is not required to start fine-tuning.
• B: You do not need to deploy the base model to an online endpoint before fine-tuning.
• C: Tracing supports observability and evaluation, but it does not prepare the fine-tuning job or dataset.

• \Pipeline1
• \Folder1\Lakehouse1

• Pipeline1 remains at the workspace root in Workspace1, so it is deployed to the root of Workspace2.
• Lakehouse1 was moved into Folder1, so its full path is preserved as \Folder1\Lakehouse1.
• Fabric deployment pipelines preserve folder paths because an item’s full path is treated as part of its name.

• Share files with the wrong people
• Use public links unnecessarily
• Fail to classify sensitive data
• Upload data to unauthorized services
• Misunderstand company sharing policies

• A — Step-up authentication: Helps protect administrator accounts, but does not directly address improper file sharing by users.
• C — Password complexity: Helps reduce password attacks, not accidental data disclosure.
• D — Mobile device management: Secures managed mobile devices, but does not directly control file-sharing behavior across the organization.

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

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

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

• 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

• Asynchronous inference is designed for applications that submit individual inference requests, place them in a queue, and retrieve results later. It is useful when requests may take a long time or when traffic is intermittent.
• Batch transform is designed specifically to run inference over an entire large dataset stored in Amazon S3 and produce an output dataset.

• Large dataset/offline processing ? Batch transform
• Large or slow individual requests processed later ? Asynchronous inference

• A class/teacher fact should contain one row per Class ID. It can support the count of classes and contain attributes such as Teacher First Name and Period Number.
• An attendance fact should contain one row per attendance event, such as Class ID + student + date. It supports attendance counts by day and monthly averages.

• Teacher First Name ? Teacher fact
• Period Number ? Attendance fact

• Accept: Acknowledges the risk without taking additional action.
• Transfer: Shifts the risk or financial impact to another party, such as an insurer.
• Mitigate: Reduces the likelihood or impact through controls like patching, MFA, or segmentation.
• Avoid: Eliminates the activity that creates the risk.

• Power BI dataset — Reuses the existing tables, relationships, and measures. You mainly create new visualizations.
• SharePoint folder — Connects to the source files, but you would need to rebuild the model and measures.
• Power BI dataflows — Primarily provide reusable data preparation; they do not automatically provide the existing report’s measures and model.
• Excel workbook — Requires reconnecting to and modeling the source data again.

• B: Não é preciso implantar o modelo em um endpoint do Amazon SageMaker, pois o Bedrock já oferece a infraestrutura de inferência.
• C: O SageMaker Model Registry é usado para gerenciar modelos no SageMaker, não é requisito para modelos customizados no Bedrock.
• D: Não existe uma etapa geral de “conceder acesso” ao modelo customizado como requisito principal de uso. O ponto essencial é adquirir o Provisioned Throughput.

• Formatting: May remove file-system references but often leaves recoverable data.
• Degaussing: Uses a magnetic field to erase data, but can damage or make magnetic drives unusable.
• Defragmentation: Rearranges data for performance; it does not securely erase information.

• Recovery Services vault — stores Site Recovery configuration and recovery metadata.
• Hyper-V site — represents the on-premises Hyper-V environment.
• Azure virtual network — the target network where the replicated VM will run after failover. Since Azure VMs already use the same virtual network, that VNet can be selected as the target.
• Storage account or managed-disk target, depending on the ASR configuration and portal version.
• Provider/agent on the Hyper-V server — enables replication from Hyper-V to Azure.

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

• Confirming the data has the required columns and data types
• Handling missing or duplicate records
• Converting data into a suitable format
• Selecting or engineering useful features
• Splitting it into training, validation, and test sets

1. Prepare the training data
2. Select an algorithm or configure AutoML
3. Train the model
4. Evaluate its performance
5. Tune hyperparameters if needed
6. Deploy the model

• Customers may boycott V’s products.
• Supermarket customers may stop buying from V.
• Investors may view V as having higher legal, ethical and reputational risk.
• V could face fines, lawsuits, contract losses and higher costs.
• Expected future profits may fall.

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

• CIA: Confidentiality, integrity, and availability—the core security objectives.
• ACL: Access Control List; rules that permit or deny traffic or access.
• PEM: A format and standard commonly associated with encoded certificates and keys.

apex 
Set<Id> accountIds = new Set<Id>{ accountId1, accountId2 }; 


List<Account> accounts = [ 
    SELECT Id, Name 
    FROM Account 
    WHERE Id IN :accountIds 
];

• A: LIMIT accepts a number, not a collection of IDs.
• B: Set.containsAll() checks set contents in Apex; it does not filter SOQL results.
• C: Database.query() accepts a dynamic SOQL string, not a Set<Id> directly.

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

1. Initiation

1. Planning

1. Execution

1. Monitoring and controlling

1. Closing

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

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