the are questions from Whozlabs Design
Patterns -
Which of the following can be contorlled centrally by MVC ?
A. database functionlaity
B. security
C. loggin
D. screen flow
E. accessing remote component
a model holds the businees logic and data base access thing. so MVC does waht is said in A, but it uses the model component to do so. So A is correct
E is incorrect because MVC is a presentaion layer pattern and has nothing to with remote access.
the POINT is option like SECURITY and LOGGING are 'NOT AT ALL RELATED TO DESIGN PATTERNS' and must never appear here. we use the
J2EE features to imlement sevurity/logging, and design patterns are never related to these issues in any way. so as per me -
only A and D are correct. but whizlabs tells to select 3 options and they are B,D,C
Another question on similar lines -
Whic hare advantages of Front Controller ?
A. improves security mangeability
B. centralizes control
C. enables seperation between presentation and web tier services
D. reduces networking calls involved and thus increases performance
E. improves reusability
my answers wer - B,C,E
whizlabs says - B,A,E
My arguement against E - security management is not a design pattern issue
its rather a J2EE spec issue and design patterns have nothing to do with it
and as J2EE says- we never code security in the source files, rather we deslare it in web.xml
i agree that C is wrong as Front Controller is a presentaion tier pattern
i expect a healthy debate on this -
security management is not a design pattern issue
its rather a J2EE spec issue and design patterns have nothing to do with it
and as J2EE says- we never code security in the source files, rather we deslare it in web.xml like SECURITY and LOGGING are 'NOT AT ALL RELATED TO DESIGN PATTERNS' and must never appear here. we use the J2EE features to imlement sevurity/logging, and design patterns are never related to these issues in any way thanks in advance !