Test Prep ASVAB Section 6: Mathematics Knowledge Exam Prep
ASVAB Section Six : Mathematics Knowledge (Page 7 )

• Business risks
• Potential financial, operational, legal, or reputational impact
• How governance reduces risk to organizational objectives
• How much risk the organization is willing to accept

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

• Leaf switches provide access ports for servers, users, and other devices.
• Spine switches provide the backbone between leaf switches.
• Every leaf switch connects to every spine switch, creating a predictable, full-mesh fabric between the two layers.
• Leaf switches do not connect directly to other leaf switches, and spine switches do not connect directly to other spine switches.

• A: Adding both a spine and leaf is unnecessary for simply adding access ports.
• B: It focuses on uplink speed, not the scalable topology.
• D: A single spine connection creates a bottleneck and a single point of failure.

• Labels control access and protection, not blanket exclusion.
• If the user has permission to open a labeled file—especially if the label allows authenticated users to view it—Copilot can use that file in a summary.
• If the label applies encryption and the user lacks the required usage rights, Copilot should not use the file or reveal its contents.
• Copilot honors the user’s existing permissions, so it should not expose labeled content to an unauthorized user.

• Early units show relatively large time savings.
• Later units still take less time, but the reduction becomes progressively smaller.
• The curve therefore becomes flatter as production approaches 256 units.

• B: The reduction is not constant; learning normally diminishes over time.
• C: Time does not reduce at an increasing rate.
• D: A steady state may eventually be reached, but the question concerns the first 255 units while learning is still occurring.

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

• Correct exam answer: A — HKEY_LOCAL_MACHINE
• The relevant location is associated with HKEY_LOCAL_MACHINE\SAM.
• The SAM does not store passwords in plain text; it stores password hashes.

• HKEY_CURRENT_USER contains settings for the currently logged-in user, not the account-password database.
• HKEY_USERS contains user profiles and settings loaded for users.
• HKEY_CURRENT_CONFIGURATION contains hardware/profile configuration information.

• terraform apply
• terraform destroy

• COE: Identifies the Center of Excellence, such as Payroll or Benefits.
• Topic Detail: Classifies the HR service within its COE; it does not identify the catalog item.
• Template: Supplies default values or case configuration.
• Record Producer: Represents the catalog item that employees use to submit the request and create the case.

• Documented and formally requested
• Analyzed for security, cost, and operational impact
• Reviewed and approved by the appropriate personnel
• Tested before implementation
• Tracked and reversible if problems occur

• Risk management process: Identifies and evaluates risk, but does not directly authorize design changes.
• Product design process: Applies primarily while creating or developing the product.
• Design review process: May have identified the issues, but the next step for changing an already released design is controlled change management.

• Suspended an operator who refused to use unsafe equipment.
• Paid another operator a bonus for using it.
• Prioritised short-term productivity over employee safety.

• A — Management is not particularly concerned with managing risks.

• B — Employees will perceive that management does not care about health and safety risks.

• C — The factory’s safety record is likely to be poor.

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

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

• Sustainability
• Performance efficiency
• Reliability

• Behavioral and anomaly detection
• Threat intelligence integration
• User and entity behavior analytics
• Automated response actions, often through SOAR integration

• Virus signatures: Associated primarily with antivirus or endpoint protection.
• Security agent deployment: Usually an endpoint-management or EDR function.
• Vulnerability scanning: Typically performed by vulnerability-management tools, though a SIEM may integrate their results.

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

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

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

• Wireshark captures packets and allows you to examine their contents, potentially revealing usernames and passwords sent without encryption.
• Netcat creates network connections and can send or receive data, but it is not primarily a packet-analysis tool.
• Nessus scans for known vulnerabilities and configuration issues; it generally would not prove that credentials are visible in transit.
• Nmap performs network discovery and port/service scanning, not detailed packet-content inspection.

• Rights issue: Raises new equity from existing shareholders. It does not increase debt or gearing, so it is least likely to breach the covenant.
• Retained earnings: Also equity finance, but the amount available may be insufficient for the required $800 million.
• Private placement of a bond: Creates additional debt and would worsen gearing, increasing the risk of breaching the covenant.
• Bank overdraft: Also debt finance, usually short-term and potentially expensive; it would still increase financial risk and gearing.

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

DAX 
Sales % of Total = 
DIVIDE( 
    [Total Sales], 
    CALCULATE( 
        [Total Sales], 
        ALLSELECTED(Products) 
    ) 
)

DAX 
Total Sales = 
SUM(Sales[SalesAmount])

Why ALLSELECTED is required

• The numerator, [Total Sales], is evaluated for the current product.
• ALLSELECTED(Products) removes the current product’s visual filter when calculating the denominator.
• It preserves filters applied at the report, page, or slicer level.

Why not ALL(Products)?

DAX 
CALCULATE([Total Sales], ALL(Products))

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

• Annual interest payments net of tax relief (A): future cash outflows for the issuer.
• Redemption value (B): the final cash outflow when the bond is redeemed.
• Market value now (C): the cash proceeds received now, acting as the initial cash flow in the IRR calculation.

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

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

• Required response and resolution times
• Availability or uptime targets
• Performance standards
• Support obligations
• Remedies or penalties for failing to meet the terms

• SOW (Statement of Work): Defines the project’s scope, tasks, deliverables, and schedule.
• MOA (Memorandum of Agreement): Describes agreed responsibilities between parties, often for a specific activity.
• MOU (Memorandum of Understanding): Records a mutual understanding or intention, usually less formal than a contract.

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

• Disable high concurrency: This changes session-sharing behavior but does not provide dedicated compute or true workload separation.
• Modify the number of executors: Adjusts resources within a Spark job; it does not isolate bronze and silver processes.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• A. Remove rows where Sales[Status] is Canceled

• E. Remove Sales[Canceled Date]

• B: Removing Sales_Date would remove information users need—the date portion.
• C: Changing Delivery_Time to Integer could alter its meaning or precision and is not necessarily safe.
• D: Splitting the date/time column creates additional columns rather than simply removing unnecessary data.

• B. Deploy to a SageMaker endpoint: This is needed for SageMaker-hosted models, not for a model intended to be used directly in Amazon Bedrock.
• C. Register with SageMaker Model Registry: SageMaker Model Registry is unrelated to invoking custom models in Bedrock.
• D. Grant access in Bedrock: Access permissions may be necessary, but they do not replace the required provisioned capacity.

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

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

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

• Firewall
• Intrusion prevention and detection
• Antivirus or antimalware
• Web and email filtering
• Virtual private networking (VPN)
• Sometimes content filtering and centralized reporting

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

• netstat -tuln can show listening TCP ports.
• If the web service is not listening, or is bound only to 127.0.0.1, remote browsers cannot connect even though the server responds to ping.

• traceroute: Tests the path to the server, but ping already confirms basic reachability.
• tcpdump: Useful for detailed packet analysis, but it is more appropriate after checking whether a service is listening.
• arp: Helps troubleshoot local IP-to-MAC resolution, not an application-layer web connection.

• Accept terms of use
• Enter a temporary code or credentials
• Provide basic registration information

• Enterprise authentication — Authenticates organizational users, often with centralized identity services; it is not specifically designed for temporary guest access.
• Ad hoc network — A temporary device-to-device network, not an authentication process.
• WPA3 — A wireless security standard. It protects Wi-Fi access but does not provide the web-based temporary access workflow described here.

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

• A. IDS attack signatures: An IDS mainly detects suspicious network traffic. It is not the best control for scanning uploaded documents.
• C. Load balancer: Distributes traffic among servers and can improve availability, but does not specifically detect malware.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection. It may inspect web requests, but malware scanning of PDF files is not its primary function.

• B — Incorporate contextual output encoding/escaping: Encode untrusted data based on its context—HTML, attribute, JavaScript, or URL—so the browser treats it as data rather than executable code.
• D — Run untrusted HTML input through an HTML sanitization engine: Sanitization removes or neutralizes dangerous elements and attributes, such as script-related content, while preserving safe HTML where needed.

• A: Enabling client-side scripts does not prevent XSS. Script restrictions may reduce risk in some environments, but “enable” is not a general XSS control.
• C: Cookie inspection is unrelated to preventing injected scripts.
• E: The SameSite cookie attribute primarily helps mitigate CSRF, not XSS. It should not generally be described as an XSS prevention measure.

• 255.255.255.128 = /25: 128 total, 126 usable
• 255.255.255.192 = /26: 64 total, 62 usable
• 255.255.255.224 = /27: 32 total, 30 usable
• 255.255.255.240 = /28: 16 total, 14 usable

• One for the network address
• One for the broadcast address

• 8 total addresses
• 6 usable addresses
• Mask: 255.255.255.248

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

• Layer 1: Check cables, power, and link lights.
• Layer 2: Check switching, VLANs, and MAC learning.
• Layer 3: Check IP addressing, routing, and gateways.
• Higher layers: Check services, applications, and user settings.

• Create a plan of action: Decide how to implement the fix.
• Implement the solution: Apply the selected fix.
• Verify functionality: Confirm the problem is resolved and systems work normally.

• Accept: Acknowledging the risk and choosing not to take additional action.
• Transfer: Shifting the risk or financial consequences to another party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or access restrictions.
• Avoid: Eliminating the activity that creates the risk.

• A. PsFile — Correct: Displays files opened remotely on a system. This reveals shared resources and user activity.
• B. UserInfo — Correct: Gathers information about user accounts, supporting account and privilege enumeration.
• C. PsPasswd — Answer key lists it: This is questionable. PsPasswd is primarily used to change passwords remotely, not enumerate information. The key may classify it broadly as a Windows account-management tool, but it is not a strong enumeration example.
• D. WinSSLMiM — Incorrect: Used for SSL man-in-the-middle activity, not enumeration.

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.

• BCP (Business Continuity Plan): è più ampio e mira a mantenere le funzioni essenziali dell’organizzazione durante un’interruzione. Il DRP è una componente più specifica del BCP.
• Communication plan: stabilisce come comunicare con dipendenti, cittadini e altre parti interessate, ma non ripristina i sistemi.
• IRP (Incident Response Plan): gestisce la risposta iniziale a un incidente di sicurezza, come un attacco informatico, non principalmente il recupero da un disastro fisico.

• DB1 (500 TB): Azure Data Box Heavy

• Virtual machines: Azure Migrate

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