Spring MVC Deep Dive Quiz

Test

Parties jouées 1 %Précision 44 Temps moyen 01:05

Créer une copie

À propos de cette activité

Challenging scenarios for Spring MVC pros

Créé par

Swati Nikam

India

Téléchargez la version pour jouer sur papier

Top 10 résultats

#	Jeux	Précision	temps
1	Vakar 18 Mars 2026	% 44	01:05

Voulez-vous apparaître dans le Top 10 de ce jeu? Connectez-vous pour vous identifier.

Créez votre propre jeu gratuite à partir de notre créateur de jeu

Affrontez vos amis pour voir qui obtient le meilleur score dans ce jeu

Créer un défi

		%
	Anonyme	%
		%
		%

Imprimez votre jeu

Spring MVC Deep Dive Quiz


Spring MVC Deep Dive QuizVersion en ligne Challenging scenarios for Spring MVC pros par Swati Nikam 1 Q1: In a typical Spring MVC app, is a bean defined in the root (parent) context visible to the web (child) context by default? a No, parent beans are isolated from the child context b Yes, parent beans are visible to the child context by default. c Only beans explicitly exposed via BeanFactory can be seen d Only if the bean is scoped@request or @session 2 Q2: Which statement best describes how ViewResolver ordering works when multiple resolvers exist? a Only the resolver with the lowest bean name is used b Resolvers are tried randomly to avoid bias c The first resolver that can resolve the view name is used, based on its order value. d All resolvers are consulted and the last successful one wins 3 Q3: What is a key difference between Model, ModelMap, and ModelAndView in a controller method? a Model is immutable while ModelMap is mutable only in POST requests b ModelAndView cannot hold a view name c Model/ModelMap carry attributes; ModelAndView wraps the model and the view together. d ModelMap cannot be used with JSP views 4 Q4: When using @SessionAttributes, when is stored data cleared from the session? a After each redirect automatically b When SessionStatus.setComplete() is called or the session ends. c Only on application shutdown d When the controller method returns a 4xx/5xx status 5 Q5: If you declare a bean with the same name in a child context, what happens? a The parent bean takes precedence b They merge into a single bean c Spring throws an immediate configuration error d The child context bean shadows the parent bean for that name within the child context. 6 Q7: Which statement about ModelAndView is true in a controller method returning String vs ModelAndView? a ModelAndView cannot be used with annotation-based controllers b ModelAndView is deprecated in modern Spring c Returning String cannot have a model d ModelAndView allows returning both a view name and a model in a single object. 7 Q8: Assertion: The child WebApplicationContext initializes after the parent, and always delegates missing beans upward. Reason: Delegation happens only for bean lookups, not during initialization. a Both assertion and reason are true, and the reason explains the assertion. b Only reason true, assertion false c Only assertion true, reason false d Both false 8 Q9: True/False: Data stored under @SessionAttributes persists across a redirect until explicitly cleared or the session ends. (Reason: Redirects do not clear the session.) a False b True c True, but only with SessionStatus.setComplete called beforehand d True, but only for flash attributes 9 Q10: Given @SessionAttributes("user") and a controller method that adds 'user' to the model, what happens after a redirect? a It becomes a request-scoped attribute b Redirect loses all session data unless flash attributes are used c The 'user' attribute remains in session until cleared or setComplete is called. d The attribute is removed immediately after redirect Feedback 1 Root-to-child visibility is the default. Child can access parent beans unless overridden by a conflicting bean in the child. 2 Resolvers are evaluated in ascending order; first resolvable view is chosen. 3 Model/ModelMap add attributes; ModelAndView combines model with the view name. 4 Session attributes persist across multiple requests until explicitly cleared or session ends. 5 Child context can override parent definitions for the same bean name. 6 ModelAndView combines view and model; returning String only provides view name unless using Model parameter. 7 Initialization order follows parent first; delegation applies to lookups, not creation order. 8 Session attributes persist across redirects unless cleared or session ends. 9 Session attributes survive redirects; use SessionStatus to clear when done.

Vous pouvez intégrer le jeu dans un LMS compatible avec LTI 1.1 ou LTI 1.3 comme Canvas, Moodle ou Blackboard. Les scores seront ainsi automatiquement enregistrés dans le carnet de notes de la plateforme.

Spring MVC Deep Dive Quiz

Test

À propos de cette activité

Créé par

Téléchargez la version pour jouer sur papier

Top Jeux

Test

Tissues - Practice Quiz

Test

Photosynthesis vs Cellular Respiration - Practice Quiz

Test

UPS 5 Seeing Habits Quiz

Test

Spanish Alphabet Listening

Test

Practice Quiz - Punnett Square, Variation, and Mutations

Spring MVC Deep Dive QuizVersion en ligne

par Swati Nikam

Q1: In a typical Spring MVC app, is a bean defined in the root (parent) context visible to the web (child) context by default?

Q2: Which statement best describes how ViewResolver ordering works when multiple resolvers exist?

Q3: What is a key difference between Model, ModelMap, and ModelAndView in a controller method?

Q4: When using @SessionAttributes, when is stored data cleared from the session?

Q5: If you declare a bean with the same name in a child context, what happens?

Q7: Which statement about ModelAndView is true in a controller method returning String vs ModelAndView?

Q8: Assertion: The child WebApplicationContext initializes after the parent, and always delegates missing beans upward. Reason: Delegation happens only for bean lookups, not during initialization.

Q9: True/False: Data stored under @SessionAttributes persists across a redirect until explicitly cleared or the session ends. (Reason: Redirects do not clear the session.)

Q10: Given @SessionAttributes("user") and a controller method that adds 'user' to the model, what happens after a redirect?

Feedback