Free C1000-208 practice test: 30 questions with answers

A return reverses an issue by sending unused material from a job back into the storeroom balance. A transfer moves stock between storerooms, a receipt records new delivery from a supplier, and a positive adjustment is for correcting balances after a count.

A transfer moves stock from one storeroom to another while it stays in inventory. Issuing against a work order removes stock for a job, returning to the vendor sends goods back to the supplier, and a receipt brings in goods bought from a supplier.

An adjustment corrects the book balance to match a verified physical count, here reducing 20 recorded units to 17. Issuing stock to a placeholder job, receiving more goods, or returning goods to the vendor would each record movements that did not happen.

Tools are issued to a job or a person and returned after use rather than consumed, so they are tracked through issue and return. Being consumed at issue, being recorded as a receipt, or reordering on every issue does not describe how tools are kept in inventory.

Issuing stock to a work order and transferring stock to another storeroom both take quantity out of the storeroom they are posted against. Receipts, returns and positive adjustments all add quantity to that storeroom.

Stock quantities are held per item for each storeroom through an inventory record, so the item must be linked to the storeroom before receipts can be tracked there. A standard cost, a planned work order or a tool record does not create a place to hold balances, so none of them is a prerequisite.

A non-stock item is bought as needed and does not carry a quantity on hand in a storeroom, which matches an adhesive bought for each repair. A bin limit, a zero reorder point or a condition code still assumes the item is held in stock, so those options do not fit.

One item can be stored in several storerooms, and each storeroom keeps its own inventory record and balance for it. Attaching the item to only one storeroom, duplicating the item master, or tracking counts outside Maximo does not give each site its own tracked quantity.

An order unit and an issue unit joined by a conversion factor let purchasing and inventory each work in the unit they need while sharing one item record. Duplicate item records, manual splitting, or one shared unit with notes leaves balances and costs inconsistent.

A stocked item's balance is kept per storeroom and, where bins are used, per bin location inside that storeroom. The vendor, the commodity code and the standard cost describe the item but do not show where its stock physically sits.

Available balance is current balance minus reserved balance, so 12 minus 5 leaves 7. The other options either ignore the reservation, use only the reserved amount, or add the reservation instead of subtracting it.

A reservation sets aside a quantity for specific planned work, which lowers the available balance so the same stock is not promised twice. Commodity codes, condition codes and non-stock items do not hold back quantities for a job.

A reorder point is the balance level that signals when replenishment should be requested, so the item can be reordered before it runs out. Standard cost, order unit conversions and condition codes do not trigger replenishment.

Raising the reorder point starts replenishment while there is still stock on hand, which gives the delivery time to arrive. Lowering it delays ordering, deleting the inventory record stops tracking the item, and changing the costing method affects valuation rather than replenishment timing.

FIFO charges issues at the cost of the oldest receipts still on hand, which is the March receipt at $40. The June price is the newest cost, the $43 simple average ignores FIFO altogether, and a preset standard cost is not used under FIFO.

Average costing weights each unit price by quantity: (100 times $10 plus 50 times $16) divided by 150 gives $12.00. The simple mean of $13.00 ignores quantities, while the latest price or the original price ignores the blended value of the stock.

Standard costing values issues at a predetermined cost held on the item, not at the prices of particular receipts. Oldest-receipt, newest-receipt and recalculated-average pricing belong to FIFO, LIFO and average costing.

A cost adjustment changes the recorded value of inventory while leaving the quantity on hand unchanged. Issuing stock to a dummy job or returning it to the vendor changes the quantity, and a count that enters the same quantity changes nothing about the value.

Cycle counting checks a rotating subset of items on a schedule, so the storeroom keeps operating while balances are verified over time. Full counts still need adjustments when they find variances, and counting only recent receipts or resetting costs does not verify balances.

A variance should be verified and its cause investigated before an adjustment brings the balance into line with the verified count. Issuing stock to a job, lowering the reorder point, or posting a receipt would hide or invent movements that did not happen.

Recording counts exactly as found, including zeros, and comparing each location with its own system balance produce accurate variances. Unrecorded issues break the match, while skipping inactive items or changing costs mid-count leaves gaps and distorts values.

Hiding the expected quantity stops counters from simply confirming the system figure, which makes the count more independent. Skipping records, removing variance review, and setting costs from estimates are not purposes of a blind count.

A receipt posts goods that arrive against an order line, so the storeroom balance rises only by what was actually delivered and the other two pumps stay open on the order. Issuing, transferring or adjusting the balance does not record a delivery from the supplier.

Returning received lines to the vendor reverses the quantity taken in for those pumps and sends them back to the supplier. Issuing to scrap or transferring to quarantine does not return goods to the supplier, and raising the balance would overstate stock.

Voiding a receipt reverses an entry that was posted in error, so the records match what was actually received. Leaving the receipt, returning goods that never arrived, or editing the order to match the entry would keep the error in the records.

The gap between ordered and received quantities is the amount still outstanding on the line, so 15 units remain to be received. Issues to a work order, reservations for another order, or a closed line would each mean something different from that figure.

Commodity groups are the higher-level classification, and commodity codes sit beneath them to classify items in more detail. A reversed hierarchy, a unit of measure, or a vendor catalogue number is not what commodity groups and codes represent.

Condition codes describe the state of stock so that items in different conditions can be told apart. Purchase price, reporting categories and bin placement are handled by other settings rather than by condition codes.

Commodity codes classify items so that spending and activity can be grouped and reported by category. Bin placement, reorder points and physical condition are set through other fields rather than through commodity codes.

A commodity group is the higher level that holds related commodity codes, so reporting at that level totals across them. Individual codes are too narrow for a combined total, while condition codes and units of measure do not group items by commodity.