You just have to encapsulate your code block in a callback class that implements the TransactionCallback interface and pass it to the TransactionTemplate execute method for execution. In this way, you don’t need to repeat the boilerplate transaction management code for this block.a) Trueb) FalseAnswer: aExplanation: In this way, you don’t need to repeat the boilerplate transaction management code for this block. 13. A TransactionTemplate can accept a transaction callback object that implements:-a) TransactionCallbackb) TransactionCallbackWithoutResult classc) All of the mentionedd) None of the mentionedAnswer: cExplanation: A TransactionTemplate can accept a transaction callback object that implements either the TransactionCallback or an instance of the one implementer of that interface provided by the framework, the TransactionCallbackWithoutResult class. 14. Spring (since version 2.0) offers a transaction advice that can be easily configured via the:-a) rx:adviceb) bx:advicec) tx:adviced) none of the mentionedAnswer: cExplanation: This advice can be enabled with the AOP configuration facilities defined in the aop saop schema. 15. You can omit the transaction-manager attribute in the element if your transaction manager has the name transactionManager.

• A. Trueb) FalseAnswer: aExplanation: In this way, you don’t need to repeat the boilerplate transaction management code for this block. 13. A TransactionTemplate can accept a transaction callback object that implements:-a) TransactionCallbackb) TransactionCallbackWithoutResult classc) All of the mentionedd) None of the mentionedAnswer: cExplanation: A TransactionTemplate can accept a transaction callback object that implements either the TransactionCallback or an instance of the one implementer of that interface provided by the framework, the TransactionCallbackWithoutResult class. 14. Spring (since version 2.0) offers a transaction advice that can be easily configured via the:-a) rx:adviceb) bx:advicec) tx:adviced) none of the mentionedAnswer: cExplanation: This advice can be enabled with the AOP configuration facilities defined in the aop saop schema. 15. You can omit the transaction-manager attribute in the element if your transaction manager has the name transactionManager.a) True
• B. FalseAnswer: aExplanation: In this way, you don’t need to repeat the boilerplate transaction management code for this block. 13. A TransactionTemplate can accept a transaction callback object that implements:-a) TransactionCallbackb) TransactionCallbackWithoutResult classc) All of the mentionedd) None of the mentionedAnswer: cExplanation: A TransactionTemplate can accept a transaction callback object that implements either the TransactionCallback or an instance of the one implementer of that interface provided by the framework, the TransactionCallbackWithoutResult class. 14. Spring (since version 2.0) offers a transaction advice that can be easily configured via the:-a) rx:adviceb) bx:advice
• C. All of the mentionedd) None of the mentionedAnswer: cExplanation: A TransactionTemplate can accept a transaction callback object that implements either the TransactionCallback or an instance of the one implementer of that interface provided by the framework, the TransactionCallbackWithoutResult class. 14. Spring (since version 2.0) offers a transaction advice that can be easily configured via the:-a) rx:adviceb) bx:advicec) tx:advice
• D. None of the mentionedAnswer: cExplanation: A TransactionTemplate can accept a transaction callback object that implements either the TransactionCallback or an instance of the one implementer of that interface provided by the framework, the TransactionCallbackWithoutResult class. 14. Spring (since version 2.0) offers a transaction advice that can be easily configured via the:-a) rx:adviceb) bx:advicec) tx:adviced) none of the mentionedAnswer: cExplanation: This advice can be enabled with the AOP configuration facilities defined in the aop saop schema. 15. You can omit the transaction-manager attribute in the element if your transaction manager has the name transactionManager.a) Trueb) FalseAnswer: aExplanation: This element will automatically detect a transaction manager with this name. You have to specify a transaction manager only when it has a different name.Sanfoundry Global Education & Learning Series – Java Spring.To practice all areas of Java Spring, here is complete set of 1000+ Multiple Choice Questions and Answers.Participate in the Sanfoundry Certification contest to get free Certificate of Merit. Join our social networks below and stay updated with latest contests, videos, internships and jobs!Telegram | Youtube | LinkedIn | Instagram | Facebook | Twitter | PinterestYoutube | LinkedIn | Instagram | Facebook | Twitter | Pinterest« Prev - Spring Questions and Answers – Hibernate and JPA Contextual Sessions» Next - Spring Questions and Answers – Setting the Transaction Attribute