

MCQOPTIONS
Saved Bookmarks
This section includes 2 Mcqs, each offering curated multiple-choice questions to sharpen your Spring knowledge and support exam preparation. Choose a topic below to get started.
1. |
A splitter takes an input message and asks you, the user of the component, on what basis it should split the Message.a) Trueb) FalseAnswer: aExplanation: You’re responsible for providing the split functionality.3. Spring Integration ships with useful splitters that require no customization.a) Splitterb) XPathMessageSplitterc) All of the mentionedd) None of the mentionedAnswer: bExplanation: In a few cases, Spring Integration ships with useful splitters that require no customization. One example is the splitter provided to partition an XML payload along an XPath query, XPathMessageSplitter.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("e5da93a0-b61a-4789-96be-a57ebec165b0"); });/**/advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("7cee830d-5f11-4a2b-b356-93cc453475a0"); });/**/4. Return type of the method annotated by the @Splitter annotation is of type:-a) java.util.Collectionb) java.util.Datec) all of the mentionedd) none of the mentionedAnswer: aExplanation: The configuration for this is not terribly different from the previous solutions. The Java code is just about the same as well, except that the return type of the method annotated by the @Splitter annotation is of type java.util.Collection.5. Annotation which collects a series of messages (based on some correlation that you help Spring Integration make between the messages).a) @Afterb) @Splitterc) @Aggregatord) None of the mentionedAnswer: cExplanation: An @Aggregator collects a series of messages (based on some correlation that you help Spring Integration make between the messages) and publishes a single message to the components downstream.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("fdd9bf87-4faf-4493-82b4-e5538b31931a"); });/**/6. To determine how many messages to read until it can stop:-a) SequenceSizeCompletionStrategyb) SequenceSizeCompletionc) SequenceSized) None of the mentionedAnswer: aExplanation: There are many ways for Spring Integration to correlate incoming messages. To determine how many messages to read until it can stop, it uses the class SequenceSizeCompletionStrategy, which reads a well known header value (aggregators are often used after a splitter.7. For correlation when you might not have a size but know that you’re expecting messages that share a common header value within a known time, Spring Integration provides the HeaderAttributeCorrelationStrategy.a) Trueb) FalseAnswer: aExplanation: In this way, it knows that all messages with that value are from the same group, in the same way that your last name identifies you as being part of a larger group.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("21eae76a-c83f-42b0-aec5-01d590a53f37"); });/**/8. The only custom logic is a POJO with an @Aggregator annotation on a method expecting a collection of Message objects.a) Trueb) FalseAnswer: aExplanation: It could, of course, be a collection of Customer objects, because they are what you’re expecting as output from the previous splitter.9. You want to conditionally move a message through different processes based on some criteria.a) router componentb) EAIc) all of the mentionedd) none of the mentionedAnswer: aExplanation: You can use a router component to alter the processing flow based on some predicate. You can also use a router to multicast a message to many subscribers (as you did with the splitter).advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("90f55663-effd-4105-b1e7-29d86b526544"); });/**/10. There are some convenient default routers available to fill common needs:-a) PayloadTypeRouterb) PayloadTypec) Payloadd) None of the mentionedAnswer: aExplanation: There are some convenient default routers available to fill common needs, such as payload-type–based routing (PayloadTypeRouter) and routing to a group or list of channels (RecipientListRouter).11. To receive messages from an external system and process them using Spring Integration.a) channelb) channel adapterc) EJPd) none of the mentionedAnswer: bExplanation: Spring Integration makes it trivially easy to build one.12. Adapters are opaque in nature.a) Trueb) FalseAnswer: aExplanation: Your external system interfaces with the adapter.13. Sometimes, functionality is made available from within the application via:-a) Stable APIb) Cohesive APIc) All of the mentionedd) None of the mentionedAnswer: cExplanation: Sometimes, functionality is made available from within the application via a cohesive, stable API but in a component model or form that isn’t directly accessible to the bus.14. You use Spring Integration’s inbound-channel-adapter element to wire the TwitterMessageSource and a poller element.a) Trueb) FalseAnswer: aExplanation: The poller element is configured to run every 10 seconds and to consume as many as 100 messages each time it runs.15. The API surfaces a Paging object, which works something like Criteria in Hibernate. |
A. | Trueb) FalseAnswer: aExplanation: You’re responsible for providing the split functionality.3. Spring Integration ships with useful splitters that require no customization.a) Splitterb) XPathMessageSplitterc) All of the mentionedd) None of the mentionedAnswer: bExplanation: In a few cases, Spring Integration ships with useful splitters that require no customization. One example is the splitter provided to partition an XML payload along an XPath query, XPathMessageSplitter.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("e5da93a0-b61a-4789-96be-a57ebec165b0"); });/**/advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("7cee830d-5f11-4a2b-b356-93cc453475a0"); });/**/4. Return type of the method annotated by the @Splitter annotation is of type:-a) java.util.Collectionb) java.util.Datec) all of the mentionedd) none of the mentionedAnswer: aExplanation: The configuration for this is not terribly different from the previous solutions. The Java code is just about the same as well, except that the return type of the method annotated by the @Splitter annotation is of type java.util.Collection.5. Annotation which collects a series of messages (based on some correlation that you help Spring Integration make between the messages).a) @Afterb) @Splitterc) @Aggregatord) None of the mentionedAnswer: cExplanation: An @Aggregator collects a series of messages (based on some correlation that you help Spring Integration make between the messages) and publishes a single message to the components downstream.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("fdd9bf87-4faf-4493-82b4-e5538b31931a"); });/**/6. To determine how many messages to read until it can stop:-a) SequenceSizeCompletionStrategyb) SequenceSizeCompletionc) SequenceSized) None of the mentionedAnswer: aExplanation: There are many ways for Spring Integration to correlate incoming messages. To determine how many messages to read until it can stop, it uses the class SequenceSizeCompletionStrategy, which reads a well known header value (aggregators are often used after a splitter.7. For correlation when you might not have a size but know that you’re expecting messages that share a common header value within a known time, Spring Integration provides the HeaderAttributeCorrelationStrategy.a) Trueb) FalseAnswer: aExplanation: In this way, it knows that all messages with that value are from the same group, in the same way that your last name identifies you as being part of a larger group.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("21eae76a-c83f-42b0-aec5-01d590a53f37"); });/**/8. The only custom logic is a POJO with an @Aggregator annotation on a method expecting a collection of Message objects.a) Trueb) FalseAnswer: aExplanation: It could, of course, be a collection of Customer objects, because they are what you’re expecting as output from the previous splitter.9. You want to conditionally move a message through different processes based on some criteria.a) router componentb) EAIc) all of the mentionedd) none of the mentionedAnswer: aExplanation: You can use a router component to alter the processing flow based on some predicate. You can also use a router to multicast a message to many subscribers (as you did with the splitter).advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("90f55663-effd-4105-b1e7-29d86b526544"); });/**/10. There are some convenient default routers available to fill common needs:-a) PayloadTypeRouterb) PayloadTypec) Payloadd) None of the mentionedAnswer: aExplanation: There are some convenient default routers available to fill common needs, such as payload-type–based routing (PayloadTypeRouter) and routing to a group or list of channels (RecipientListRouter).11. To receive messages from an external system and process them using Spring Integration.a) channelb) channel adapterc) EJPd) none of the mentionedAnswer: bExplanation: Spring Integration makes it trivially easy to build one.12. Adapters are opaque in nature.a) Trueb) FalseAnswer: aExplanation: Your external system interfaces with the adapter.13. Sometimes, functionality is made available from within the application via:-a) Stable APIb) Cohesive APIc) All of the mentionedd) None of the mentionedAnswer: cExplanation: Sometimes, functionality is made available from within the application via a cohesive, stable API but in a component model or form that isn’t directly accessible to the bus.14. You use Spring Integration’s inbound-channel-adapter element to wire the TwitterMessageSource and a poller element.a) Trueb) FalseAnswer: aExplanation: The poller element is configured to run every 10 seconds and to consume as many as 100 messages each time it runs.15. The API surfaces a Paging object, which works something like Criteria in Hibernate.a) True |
B. | FalseAnswer: aExplanation: You’re responsible for providing the split functionality.3. Spring Integration ships with useful splitters that require no customization.a) Splitterb) XPathMessageSplitterc) All of the mentionedd) None of the mentionedAnswer: bExplanation: In a few cases, Spring Integration ships with useful splitters that require no customization. One example is the splitter provided to partition an XML payload along an XPath query, XPathMessageSplitter.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("e5da93a0-b61a-4789-96be-a57ebec165b0"); });/**/advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("7cee830d-5f11-4a2b-b356-93cc453475a0"); });/**/4. Return type of the method annotated by the @Splitter annotation is of type:-a) java.util.Collectionb) java.util.Datec) all of the mentionedd) none of the mentionedAnswer: aExplanation: The configuration for this is not terribly different from the previous solutions. The Java code is just about the same as well, except that the return type of the method annotated by the @Splitter annotation is of type java.util.Collection.5. Annotation which collects a series of messages (based on some correlation that you help Spring Integration make between the messages).a) @Afterb) @Splitterc) @Aggregatord) None of the mentionedAnswer: cExplanation: An @Aggregator collects a series of messages (based on some correlation that you help Spring Integration make between the messages) and publishes a single message to the components downstream.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("fdd9bf87-4faf-4493-82b4-e5538b31931a"); });/**/6. To determine how many messages to read until it can stop:-a) SequenceSizeCompletionStrategyb) SequenceSizeCompletionc) SequenceSized) None of the mentionedAnswer: aExplanation: There are many ways for Spring Integration to correlate incoming messages. To determine how many messages to read until it can stop, it uses the class SequenceSizeCompletionStrategy, which reads a well known header value (aggregators are often used after a splitter.7. For correlation when you might not have a size but know that you’re expecting messages that share a common header value within a known time, Spring Integration provides the HeaderAttributeCorrelationStrategy.a) Trueb) FalseAnswer: aExplanation: In this way, it knows that all messages with that value are from the same group, in the same way that your last name identifies you as being part of a larger group.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("21eae76a-c83f-42b0-aec5-01d590a53f37"); });/**/8. The only custom logic is a POJO with an @Aggregator annotation on a method expecting a collection of Message objects.a) Trueb) FalseAnswer: aExplanation: It could, of course, be a collection of Customer objects, because they are what you’re expecting as output from the previous splitter.9. You want to conditionally move a message through different processes based on some criteria.a) router componentb) EAIc) all of the mentionedd) none of the mentionedAnswer: aExplanation: You can use a router component to alter the processing flow based on some predicate. You can also use a router to multicast a message to many subscribers (as you did with the splitter).advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("90f55663-effd-4105-b1e7-29d86b526544"); });/**/10. There are some convenient default routers available to fill common needs:-a) PayloadTypeRouterb) PayloadTypec) Payloadd) None of the mentionedAnswer: aExplanation: There are some convenient default routers available to fill common needs, such as payload-type–based routing (PayloadTypeRouter) and routing to a group or list of channels (RecipientListRouter).11. To receive messages from an external system and process them using Spring Integration.a) channelb) channel adapterc) EJPd) none of the mentionedAnswer: bExplanation: Spring Integration makes it trivially easy to build one.12. Adapters are opaque in nature.a) Trueb) FalseAnswer: aExplanation: Your external system interfaces with the adapter.13. Sometimes, functionality is made available from within the application via:-a) Stable APIb) Cohesive API |
C. | All of the mentionedd) None of the mentionedAnswer: bExplanation: In a few cases, Spring Integration ships with useful splitters that require no customization. One example is the splitter provided to partition an XML payload along an XPath query, XPathMessageSplitter.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("e5da93a0-b61a-4789-96be-a57ebec165b0"); });/**/advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("7cee830d-5f11-4a2b-b356-93cc453475a0"); });/**/4. Return type of the method annotated by the @Splitter annotation is of type:-a) java.util.Collectionb) java.util.Datec) all of the mentionedd) none of the mentionedAnswer: aExplanation: The configuration for this is not terribly different from the previous solutions. The Java code is just about the same as well, except that the return type of the method annotated by the @Splitter annotation is of type java.util.Collection.5. Annotation which collects a series of messages (based on some correlation that you help Spring Integration make between the messages).a) @Afterb) @Splitterc) @Aggregatord) None of the mentionedAnswer: cExplanation: An @Aggregator collects a series of messages (based on some correlation that you help Spring Integration make between the messages) and publishes a single message to the components downstream.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("fdd9bf87-4faf-4493-82b4-e5538b31931a"); });/**/6. To determine how many messages to read until it can stop:-a) SequenceSizeCompletionStrategyb) SequenceSizeCompletionc) SequenceSized) None of the mentionedAnswer: aExplanation: There are many ways for Spring Integration to correlate incoming messages. To determine how many messages to read until it can stop, it uses the class SequenceSizeCompletionStrategy, which reads a well known header value (aggregators are often used after a splitter.7. For correlation when you might not have a size but know that you’re expecting messages that share a common header value within a known time, Spring Integration provides the HeaderAttributeCorrelationStrategy.a) Trueb) FalseAnswer: aExplanation: In this way, it knows that all messages with that value are from the same group, in the same way that your last name identifies you as being part of a larger group.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("21eae76a-c83f-42b0-aec5-01d590a53f37"); });/**/8. The only custom logic is a POJO with an @Aggregator annotation on a method expecting a collection of Message objects.a) Trueb) FalseAnswer: aExplanation: It could, of course, be a collection of Customer objects, because they are what you’re expecting as output from the previous splitter.9. You want to conditionally move a message through different processes based on some criteria.a) router componentb) EAIc) all of the mentionedd) none of the mentionedAnswer: aExplanation: You can use a router component to alter the processing flow based on some predicate. You can also use a router to multicast a message to many subscribers (as you did with the splitter).advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("90f55663-effd-4105-b1e7-29d86b526544"); });/**/10. There are some convenient default routers available to fill common needs:-a) PayloadTypeRouterb) PayloadTypec) Payloadd) None of the mentionedAnswer: aExplanation: There are some convenient default routers available to fill common needs, such as payload-type–based routing (PayloadTypeRouter) and routing to a group or list of channels (RecipientListRouter).11. To receive messages from an external system and process them using Spring Integration.a) channelb) channel adapterc) EJPd) none of the mentionedAnswer: bExplanation: Spring Integration makes it trivially easy to build one.12. Adapters are opaque in nature.a) Trueb) FalseAnswer: aExplanation: Your external system interfaces with the adapter.13. Sometimes, functionality is made available from within the application via:-a) Stable APIb) Cohesive APIc) All of the mentioned |
D. | None of the mentionedAnswer: bExplanation: In a few cases, Spring Integration ships with useful splitters that require no customization. One example is the splitter provided to partition an XML payload along an XPath query, XPathMessageSplitter.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("e5da93a0-b61a-4789-96be-a57ebec165b0"); });/**/advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("7cee830d-5f11-4a2b-b356-93cc453475a0"); });/**/4. Return type of the method annotated by the @Splitter annotation is of type:-a) java.util.Collectionb) java.util.Datec) all of the mentionedd) none of the mentionedAnswer: aExplanation: The configuration for this is not terribly different from the previous solutions. The Java code is just about the same as well, except that the return type of the method annotated by the @Splitter annotation is of type java.util.Collection.5. Annotation which collects a series of messages (based on some correlation that you help Spring Integration make between the messages).a) @Afterb) @Splitterc) @Aggregatord) None of the mentionedAnswer: cExplanation: An @Aggregator collects a series of messages (based on some correlation that you help Spring Integration make between the messages) and publishes a single message to the components downstream.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("fdd9bf87-4faf-4493-82b4-e5538b31931a"); });/**/6. To determine how many messages to read until it can stop:-a) SequenceSizeCompletionStrategyb) SequenceSizeCompletionc) SequenceSized) None of the mentionedAnswer: aExplanation: There are many ways for Spring Integration to correlate incoming messages. To determine how many messages to read until it can stop, it uses the class SequenceSizeCompletionStrategy, which reads a well known header value (aggregators are often used after a splitter.7. For correlation when you might not have a size but know that you’re expecting messages that share a common header value within a known time, Spring Integration provides the HeaderAttributeCorrelationStrategy.a) Trueb) FalseAnswer: aExplanation: In this way, it knows that all messages with that value are from the same group, in the same way that your last name identifies you as being part of a larger group.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("21eae76a-c83f-42b0-aec5-01d590a53f37"); });/**/8. The only custom logic is a POJO with an @Aggregator annotation on a method expecting a collection of Message objects.a) Trueb) FalseAnswer: aExplanation: It could, of course, be a collection of Customer objects, because they are what you’re expecting as output from the previous splitter.9. You want to conditionally move a message through different processes based on some criteria.a) router componentb) EAIc) all of the mentionedd) none of the mentionedAnswer: aExplanation: You can use a router component to alter the processing flow based on some predicate. You can also use a router to multicast a message to many subscribers (as you did with the splitter).advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("90f55663-effd-4105-b1e7-29d86b526544"); });/**/10. There are some convenient default routers available to fill common needs:-a) PayloadTypeRouterb) PayloadTypec) Payloadd) None of the mentionedAnswer: aExplanation: There are some convenient default routers available to fill common needs, such as payload-type–based routing (PayloadTypeRouter) and routing to a group or list of channels (RecipientListRouter).11. To receive messages from an external system and process them using Spring Integration.a) channelb) channel adapterc) EJPd) none of the mentionedAnswer: bExplanation: Spring Integration makes it trivially easy to build one.12. Adapters are opaque in nature.a) Trueb) FalseAnswer: aExplanation: Your external system interfaces with the adapter.13. Sometimes, functionality is made available from within the application via:-a) Stable APIb) Cohesive APIc) All of the mentionedd) None of the mentionedAnswer: cExplanation: Sometimes, functionality is made available from within the application via a cohesive, stable API but in a component model or form that isn’t directly accessible to the bus.14. You use Spring Integration’s inbound-channel-adapter element to wire the TwitterMessageSource and a poller element.a) Trueb) FalseAnswer: aExplanation: The poller element is configured to run every 10 seconds and to consume as many as 100 messages each time it runs.15. The API surfaces a Paging object, which works something like Criteria in Hibernate.a) Trueb) FalseAnswer: aExplanation: You can configure how many results to return using the count property. The most interesting option is called the sinceId, which lets you search for all records occurring after the Status having the ID equal to the value given as the sinceId.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 – Transformation and Error handling» Next - Spring Questions and Answers – Spring Batch and Gateways |
Answer» B. FalseAnswer: aExplanation: You’re responsible for providing the split functionality.3. Spring Integration ships with useful splitters that require no customization.a) Splitterb) XPathMessageSplitterc) All of the mentionedd) None of the mentionedAnswer: bExplanation: In a few cases, Spring Integration ships with useful splitters that require no customization. One example is the splitter provided to partition an XML payload along an XPath query, XPathMessageSplitter.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("e5da93a0-b61a-4789-96be-a57ebec165b0"); });/**/advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("7cee830d-5f11-4a2b-b356-93cc453475a0"); });/**/4. Return type of the method annotated by the @Splitter annotation is of type:-a) java.util.Collectionb) java.util.Datec) all of the mentionedd) none of the mentionedAnswer: aExplanation: The configuration for this is not terribly different from the previous solutions. The Java code is just about the same as well, except that the return type of the method annotated by the @Splitter annotation is of type java.util.Collection.5. Annotation which collects a series of messages (based on some correlation that you help Spring Integration make between the messages).a) @Afterb) @Splitterc) @Aggregatord) None of the mentionedAnswer: cExplanation: An @Aggregator collects a series of messages (based on some correlation that you help Spring Integration make between the messages) and publishes a single message to the components downstream.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("fdd9bf87-4faf-4493-82b4-e5538b31931a"); });/**/6. To determine how many messages to read until it can stop:-a) SequenceSizeCompletionStrategyb) SequenceSizeCompletionc) SequenceSized) None of the mentionedAnswer: aExplanation: There are many ways for Spring Integration to correlate incoming messages. To determine how many messages to read until it can stop, it uses the class SequenceSizeCompletionStrategy, which reads a well known header value (aggregators are often used after a splitter.7. For correlation when you might not have a size but know that you’re expecting messages that share a common header value within a known time, Spring Integration provides the HeaderAttributeCorrelationStrategy.a) Trueb) FalseAnswer: aExplanation: In this way, it knows that all messages with that value are from the same group, in the same way that your last name identifies you as being part of a larger group.advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("21eae76a-c83f-42b0-aec5-01d590a53f37"); });/**/8. The only custom logic is a POJO with an @Aggregator annotation on a method expecting a collection of Message objects.a) Trueb) FalseAnswer: aExplanation: It could, of course, be a collection of Customer objects, because they are what you’re expecting as output from the previous splitter.9. You want to conditionally move a message through different processes based on some criteria.a) router componentb) EAIc) all of the mentionedd) none of the mentionedAnswer: aExplanation: You can use a router component to alter the processing flow based on some predicate. You can also use a router to multicast a message to many subscribers (as you did with the splitter).advertisement/**/ var adpushup = adpushup || {}; adpushup.que = adpushup.que || []; adpushup.que.push(function() { adpushup.triggerAd("90f55663-effd-4105-b1e7-29d86b526544"); });/**/10. There are some convenient default routers available to fill common needs:-a) PayloadTypeRouterb) PayloadTypec) Payloadd) None of the mentionedAnswer: aExplanation: There are some convenient default routers available to fill common needs, such as payload-type–based routing (PayloadTypeRouter) and routing to a group or list of channels (RecipientListRouter).11. To receive messages from an external system and process them using Spring Integration.a) channelb) channel adapterc) EJPd) none of the mentionedAnswer: bExplanation: Spring Integration makes it trivially easy to build one.12. Adapters are opaque in nature.a) Trueb) FalseAnswer: aExplanation: Your external system interfaces with the adapter.13. Sometimes, functionality is made available from within the application via:-a) Stable APIb) Cohesive API | |
2. |
To fork the process flow from one component to many, either all at once or to a single one based on a predicate condition. |
A. | splitter |
B. | fork |
C. | all of the mentioned |
D. | none of the mentioned |
Answer» B. fork | |