APICS CPIM Exam Prep
Certified in Production and Inventory Management (Page 30 )

• A — Improved management of storage space: Correct.

• B — Improved supplier relationships: Correct.

• C — Improved pricing decisions: Correct.

• D — Non-product-specific costs must be apportioned: Incorrect.

• E — Profitability of each customer group: Incorrect.

• A: Describes a broad purpose and direction, but is not the specific CIMA definition.
• C: “Scoping out” activities is too vague and incomplete.
• D: Combines long-term goals, strategies and policies, but describes a wider strategic-planning statement rather than the definition of strategy itself.

• Password spraying: Tries a few common passwords against many accounts; no indication of repeated login attempts.
• Remote-access Trojan (RAT): Could install malware, but it does not explain how the attacker obtained the administrator’s credentials.
• Dictionary attack: Tries words or common passwords against an account; again, the scenario specifically highlights Telnet’s lack of encryption.

• Code suggestions: Inline completions as you write code, such as lines, functions, or blocks.
• Chat: An interactive interface for asking questions, explaining code, generating code, and helping with debugging.

• Knowledge Base: Not listed as a standard Copilot Individual IDE feature in this context.
• Pull Request Diff Analysis: More closely associated with GitHub-based code review or pull-request features, not the core Individual IDE extension capabilities.

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

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

• Accept: Acknowledging the risk without taking additional action.
• Transfer: Shifting the risk’s impact to a third party, such as through insurance or outsourcing.
• Mitigate: Reducing the likelihood or impact of the risk through security controls.
• Avoid: Eliminating the activity or process that creates the risk.

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

• STP elects the switch with the lowest Bridge ID as the root bridge.
• The Bridge ID consists mainly of bridge priority + MAC address.
• If multiple switches have the same priority, the switch with the lower MAC address is preferred.
• STP bridge priority values are configured in increments of 4096, such as 0, 4096, 8192, and so on. 32768 is the standard default value.

• No servers or database infrastructure to provision.
• Uses standard SQL.
• Supports formats such as JSON, CSV, Parquet, and ORC.
• You typically define the table structure with AWS Glue Data Catalog or Athena’s own schema definitions.
• Charges are generally based on the amount of data scanned, so partitioning and columnar formats can reduce cost.
• It does not copy the data into a separate database; it reads the files in S3 when you run a query.

• Red team: Simulates attackers; exploits weaknesses to test security.
• Blue team: Defends systems; monitors, detects, and responds to attacks.
• Purple team: Combines red- and blue-team efforts to improve detection and defense.
• White team: Oversees or manages the test, defining rules, scope, and authorization.

Statement 1 — Correct

Statement 2 — Correct

• Default network device credentials: More associated with external attackers or poor device configuration.
• Spear phishing emails: Commonly used to compromise users, but less characteristic of an insider who already has access.
• Typosquatting and impersonation: Primarily social-engineering techniques aimed at deceiving users.
• Unidentified removable devices: Provide a direct way to transfer data outside the organization and may bypass network monitoring.

• A. Microsoft 365 group with Assigned membership
• C. Microsoft 365 group with Dynamic User membership

Why?

• Assigned membership: You explicitly add User1, User2, and User3.
• Dynamic User membership: Membership is automatically determined by a rule based on user attributes.

Why the other options are incorrect

• B and D: Security groups do not support the Microsoft 365 group expiration policy.
• E: Dynamic Device groups are intended for devices, not these users, and are also security groups.

• A — Use getRecordTypeInfosByDeveloperName()

apex 
  Id rtId = Schema.SObjectType.Account 
      .getRecordTypeInfosByDeveloperName() 
      .get('Business_Account') 
      .getRecordTypeId();

• C — Query the RecordType object

apex 
  RecordType rt = [ 
      SELECT Id 
      FROM RecordType 
      WHERE SObjectType = 'Account' 
      AND Name = 'Business Account' 
      LIMIT 1 
  ];

• B: An outbound SOAP call is unnecessary and inefficient.
• D: Hardcoding an ID is not dynamic, and IDs can differ between orgs.

1. Identify the fact table

• Records something that happened, such as a sale, test, appointment, or measurement
• Contains foreign keys to other tables
• Contains measures or numeric results
• Has many rows

2. Identify a dimension table

• Describe people, products, dates, locations, or departments
• Contain descriptive columns
• Are referenced by the fact table
• Have fewer rows than the fact table

3. Identify the surrogate key

• System-generated
• Unique within the dimension
• Often named PatientKey, CustomerKey, or similar
• Usually an integer
• Not meaningful outside the model

• Prevention costs – costs incurred to stop defects occurring, such as staff training, quality planning and supplier evaluation.
• Appraisal costs – costs of checking whether products meet standards, such as inspection, testing and quality audits.
• Internal failure costs – costs of defects found before delivery to customers, such as scrap, rework and retesting.
• External failure costs – costs of defects found after delivery, such as warranty claims, returns, complaints and product recalls.

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

1. Search & Intelligence in the Microsoft 365 admin center — No

1. Audit in the Microsoft Defender portal — Yes

1. Audit in the Microsoft Purview portal — Yes

• Economy: Obtaining inputs at the lowest appropriate cost.
• Efficiency: Making the best use of resources, such as staff, money, and equipment.
• Effectiveness: Achieving the intended objectives or outcomes.

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

• Build, measure, learn: Create something, assess real feedback or results, and adapt.
• Minimum viable product (MVP): Produce the smallest useful version to test assumptions and reduce uncertainty.
• Fail fast: Test ideas early so that unsuccessful approaches can be identified before significant time or cost is invested.

• File is shared externally ? Access level

• File is labeled “Internal only” ? Sensitivity label

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

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

• transform() — modifies every element in an array
• filter() — keeps elements matching a condition
• exists() — checks whether any element matches
• aggregate() — reduces array elements to one result

sql 
SELECT transform(scores, x -> x * 2) 
FROM student_scores;

• A is incorrect because higher-order functions are mainly useful for nested or complex data.
• B is incorrect because they do not convert logic into Python.
• D is incorrect because their purpose is not to fix slow built-in functions, but to process arrays or maps with custom logic.

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.

• Employees can work from any location, including remote sites and offices worldwide.
• Login can be relatively seamless after the device is registered.
• It does not require distributing additional physical authentication equipment.

• Geotagging: Identifies location, but location alone is not a strong authentication method and may prevent legitimate remote access.
• Smart cards: Provide strong authentication but require card readers and physical cards, increasing equipment and management requirements.
• Time-based logins: Typically involve one-time codes that users must enter, making the experience less seamless and potentially requiring a token or authenticator app.

• Penetration test: Tests for exploitable vulnerabilities; it does not provide a broad opinion on whether security controls operate effectively.
• Annual self-assessment: Not independent, so it provides less assurance.
• Allow each client the right to audit: Inefficient because every customer may conduct a separate audit, creating duplicated effort and disruption.

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

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

• Highly polished, organization-wide presentations
• Advanced dashboard design and customization
• Broader business-user distribution and interaction
• Specialized BI governance and modeling features

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

• Documented and evaluated
• Assessed for security, cost, and operational impact
• Reviewed and approved by the appropriate personnel
• Tested before implementation
• Tracked with version history and rollback procedures

• Risk management process: May help assess the issues, but it does not authorize and manage design changes.
• Product design process: Applies primarily while creating a new design.
• Design review process: Normally evaluates a design before release; this design is already released.

• terraform apply
• terraform destroy

• The requirement is to obtain an assessment of the Azure environment’s design.
• The proposed solution is the Premier support plan.
• Premier can provide this type of guidance, but it is a higher-tier, more expensive option.
• The question specifically says to keep costs to a minimum. A lower tier—typically Professional Direct in the support-plan model used by this question—provides architectural/design guidance.

• MFA adds an additional authentication factor, such as a phone notification or verification code.
• It helps prevent unauthorized sign-ins, even if a password is compromised.
• It does not encrypt, store, or protect credentials used by deployment processes.

• Laws and regulations
• Litigation holds
• Industry or contractual obligations
• Tax, financial, health, or privacy requirements

• Business strategy and direction: May influence retention, but cannot override legal requirements.
• Storage capacity and longevity: Practical considerations, not the primary driver.
• Business ease and value analysis: May support decisions after compliance obligations are identified.

• Encryption to preserve confidentiality
• Integrity protection to detect alteration
• Authentication of the server through certificates

• SHA-256: A hashing algorithm; it does not encrypt data for transmission.
• SSL 3.0: Obsolete and insecure. It should not be used.
• AES-256: A strong encryption algorithm, but by itself it does not provide the complete secure communication protocol needed for data in transit.

• 16GB RAM: A 64-bit OS is needed to use more than roughly 4GB effectively, but RAM capacity does not prove the CPU supports 64-bit operation.
• 500GB HDD: Storage capacity has no bearing on OS architecture.
• 1Gbps Ethernet: Network speed is unrelated to CPU architecture.

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

• Transfer — przeniesienie skutków lub kosztów ryzyka na inna organizacje, np. przez ubezpieczenie lub umowe.
• Akceptacja — firma swiadomie przyjmuje ryzyko bez dodatkowych dzialan.
• Mitigacja — zmniejszenie prawdopodobienstwa wystapienia ryzyka lub jego wplywu, np. przez wdrozenie kontroli bezpieczenstwa.
• Unikanie — calkowite wyeliminowanie ryzykownej dzialalnosci.

• Crash cart: Provides local physical access, not remote access.
• Jump box: A secured intermediary used to reach devices over the normal network; it may be inaccessible if the appliance has not booted.
• Secure Shell (SSH): Requires the device’s operating system and network services to be running properly.

• Fileless malware: Nothing in the command indicates malware executing only in memory.
• Living-off-the-land binaries: Mimikatz is a credential-access tool, not a normal system utility used for LOLBin abuse.
• Social engineering: The command shows technical credential abuse, not manipulation of an accountant.

• Restrict a port to a defined number of MAC addresses
• Use statically assigned or “sticky” MAC addresses
• Shut down or restrict the port when violations occur

• Load balancer: Distributes application traffic; it does not protect switch MAC tables.
• IPS: May detect suspicious network activity, but is not the primary control for limiting switch MAC entries.
• NGFW: Filters traffic at the network boundary; it does not directly prevent MAC table flooding on access switches.

• Azure Machine Learning is the overall Azure service.
• Machine Learning designer is the visual, drag-and-drop interface within Azure Machine Learning.
• Microsoft may refer to the broader product as Azure Machine Learning studio, while “Designer” remains the specific visual workflow tool.

• Azure Logic Apps: Workflow and integration automation.
• Azure Batch: Large-scale parallel or batch compute.
• Azure Cosmos DB: Globally distributed NoSQL database.

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

• Data loss prevention (DLP): Helps detect or prevent sensitive data from being copied or transmitted, but it does not primarily protect a stolen laptop’s stored data.
• Operating system hardening: Reduces vulnerabilities and attack surface but does not encrypt files if the device is stolen.
• Boot security: Helps ensure that only trusted software starts, but it does not fully protect the drive if an attacker accesses it offline.

• 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\)

• Honeypots: Decoy systems or services made to attract attackers. Legitimate users should not interact with them, so activity there is a strong indicator of malicious behavior.
• DNS sinkholes: Redirect requests for known malicious domains to a controlled internal system. This can reveal infected hosts attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens.
• CI/CD: Automates software development, testing, and deployment.
• Threat modeling: Identifies and analyzes potential threats before or during system design.
• Data obfuscation: Makes data harder to understand or interpret.