Inventory Practice 3

Question 1

CustomerBills are timestamped when the server takes customers’ orders and CustomerPayments are timestamped when customer payments are recorded. The tables required to calculate how long customers stay for a meal are:

Question options:

CustomerBill, FoodItem

CustomerBillItem, CustomerPayment

CustomerBill, CustomerBillLineItem

CustomerBill, CustomerPayment

BillTimestamp from CustomerBill is required to get the start time for the customer’s stay and PaymentTimestamp from CustomerPayment is required to get the end time.

Question 2

To designate food categories, someone suggested using criteria on the FoodID attribute. This is a:

Question options:

good idea because the criteria are easy to implement

good idea because the criteria can be changed easily

bad idea because it cannot be made to work correctly

bad idea because it multiplies the number of queries

View Feedback

Question 3

The EatFresh database has insufficient data for:

Question options:

calculating the dollar amount of shrinkage of food in storage by week

distinguishing between dining-and-dashing and servers pocketing cash

determining whether paleo or traditional diners are more profitable

identifying when vendors increase prices for the food items ordered

View Feedback

Question 4

To determine amounts that have not been paid to vendors, your assistant joined (left outer) VendorInvoice to VendorPayment and summed the amounts from the following expression. This approach:

unpaidAmount: [InvoiceAmount]-Nz([PaymentAmount])

Question options:

gives the correct value for unpaid amounts

has an incorrect join between the tables

overstates the total of unpaid amounts

understates the total of unpaid amounts

View Feedback

Question 5

A query is available that determines profitability by store. To edit this query to show profitability overall requires:

Question options:

removing an attribute from the query

adding an attribute to the query

adding a criterion to an attribute

removing a criterion from an attribute

View Feedback

Question 6

After seeing weekly values for shrinkage, the managers asked for daily values too. The best response to this request would be to:

Question options:

edit the queries to replace the week designation with a day designation

create a new query sequence to calculate the daily shrinkage values

compute a shrinkage value for the four weeks and divide by 28 (4 weeks times 7 days)

explain that daily values would simply be one seventh of the weekly values

Because inventory is taken weekly and there are only weekly orders, the best that can be achieved is a weekly computation. A daily value would simply be the weekly value divided by 7. Thus, the data are too aggregated (by week) to support daily computations for shrinkage.

Question 7

Your assistant proposed a query strategy for determining shrinkage with the following operations for shrinkage by store, by week, by food:

shrinkage = beginning inventory + purchases – food served – food wasted – ending inventory

If implemented correctly, the query results would show:

Question options:

correct values

understated values

overstated values

understated or an overstated values for shrinkage depending on the circumstances

View Feedback

Question 8

The purpose of creating an attribute with the day (yymmdd) of PITimestamp and an attribute with the day (yymmdd) of ReceivedTimestamp set to the same day of the week is to enable:

Question options:

grouping physical inventory and inventory receipts by week

grouping physical inventory and inventory receipts by day

designating inclusive criteria on timestamp attribute values

preserving timestamp attribute values for subsequent analysis

View Feedback

Question 9

Determining the quantity and dollar amount differences between purchase orders and vendor invoices is a query objective for the risk of:

Question options:

paying for food not received

determining shrinkage by store

detecting food item stock outs

calculating waste food by store

View Feedback

Question 10

Your assistant wanted to know if there was a way to avoid the processing overhead of using a sequence of queries, each of which had an outer join, in determining shrinkage. You reply that an outer join would not be needed to join PhysicalFoodCount and VendorInvoiceItem by week by store if record counts by store by week from the join are all:

Question options:

not less than the counts in VendorInvoiceItem

equal to the counts in VendorInvoiceItem

equal to the number of rows in FoodItem

equal to the number of rows in FoodItem minus 1

Want latest solution of this assignment

Submit Your Assignment Here

AssignmentHippo Features

On Time Delivery

Our motto is deliver assignment on Time. Our Expert writers deliver quality assignments to the students.

Plagiarism Free Work

Get reliable and unique assignments by using our 100% plagiarism-free.

24 X 7 Live Help

Get connected 24*7 with our Live Chat support executives to receive instant solutions for your assignment.

Services For All Subjects

Get Help with all the subjects like: Programming, Accounting, Finance, Engineering, Law and Marketing.

Best Price Guarantee

Get premium service at a pocket-friendly rate at AssignmentHippo


  • Assignment Writing Guide
  • Essay Writing Guide
  • Dissertation Writing Guide
  • Research Paper Writing Guide


  • Accounts
  • Computer Science
  • Economics
  • Engineering

Client Review

I was struggling so hard to complete my marketing assignment on brand development when I decided to finally reach to the experts of this portal. They certainly deliver perfect consistency and the desired format. The content prepared by the experts of this platform was simply amazing. I definitely owe my grades to them.

Tap to Chat
Get instant assignment help