inner class marked protected

[Anonymous]

Hi all!
Marcus Greens mock ( http://www.jchq.net/mockexams/exam2.htm ) has following question:
---
Question 57)
Which of the following statements are true?
1) Adding more classes via import statements will cause a performance overhead, only import classes you actually use.
2) Under no circumstances can a class be defined with the private modifier
3) A inner class may under some circumstances be defined with the protected modifier
4) An interface cannot be instantiated
---
It is clear that option 3 is right but what actually means "under some circumstances"? I think I would cut it out.

------------------
Antti Barck
It Solutions Consultant, NSD Oy

[Snylt Master]

Hi!
Take a look at the follwing code.
<code>
public class test{

void aMethod(){
class innerClass{
// In a method variables and classes cannot be marked with access modifiers
}
}
}
</code>
Correct me if I'm wrong

[Guoqiao Sun]

I think "under some circumstance" means sometimes it can be defined as protected. Since for top-level class, we cannnot define it as protected, but for inner class, we might define it as protected.
Correct me if i am wrong.
Guoqiao