Design a generic cache module that can be used at any level in a memory hierarchy. For example, this cache module can be "instantiated" as an L1 cache, an L2 cache, an L3 cache, and so on. Since it can be used at any level of the memory hierarchy, it will be referred to generically as CACHE throughout this specification.

Hey there: )if its a true or false question, then your answer is truehope that -take care now--ans

Ithink its overlap  i hope this : )

Answer (firmware)

(1)correct answer is d.the others are just bad syntax.by using the keyword "new" and int[] together, you create a new integer array object in memory. whenever you want to create an object without using array literals, you must use new. (by array literals, i mean a line of declaration code like int[] x = {4,6}; where you literally specify an array without using new. an array literal can only be used in the same line as declaring the array.)(2)correct answer is c. it is the only choice that returns an array and properly takes in an array reference as an argument.choices a and b do not return an array; they respectively return void (nothing at all) and a primitive double, which is not a double array.choice d has invalid syntax. looking at it, it won't properly accept any array reference you pass into the method.(3)correct answer is a.x is already defined.choice b only returns an index of the array.also, in any other method, you wouldn't write the type next to the thing being returned. choices c and d are invalid.(4)correct answer is c.choice a only accepts one.choice b requires at least two numbers.choice d only takes in an integer array reference, not integers.(5) correct choice is d.by specifying that the first argument can take in any number of ints, java will assume everything you input into the method will be an integer.theoretically it will never reach that string argument, no matter how many commas you put. this is illegal; the java compiler will complain. i don't think it'll even recognize it as a method header.