MENU
What are valid reasons for implementing business logic as a custom Spring Bean instead of as a Java Delegate? Choose 2 answers
Suggested Answer: A, C
Get Premium APSCE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
JA
Janey
10 months ago
C makes sense too, more flexibility with Script Tasks!
ME
Melodie
10 months ago
Wait, can you really guarantee access to the internal Java API with E? Sounds sketchy.
FR
Francoise
11 months ago
I think D is also valid, autowiring is super handy!
JA
James
11 months ago
B seems too restrictive, why limit it to just Service Tasks?
AN
An
11 months ago
A is definitely a reason, you can reuse the logic across workflows.
TA
Tammi
11 months ago
I practiced a similar question, and I think D is definitely right because autowiring is a big advantage of using Spring Beans.
GI
Giuseppe
11 months ago
I'm not entirely sure, but I feel like B could be a valid reason since it restricts usage to Service Tasks only.
TI
Tish
12 months ago
I think A makes sense too, since you want to reuse business logic across different workflows.
CL
Claudio
12 months ago
I remember something about using Spring Beans for better dependency management, so maybe D is a good choice?
GO
Goldie
1 year ago
I've got this one! Using a Spring Bean allows you to reuse the business logic across different workflows, which is super handy. And the ability to autowire dependencies is a big plus.
LE
Leslie
1 year ago
The ability to autowire dependencies is a good reason to use a Spring Bean, in my opinion. That way you can easily inject any other services or components your business logic needs.
BE
Bernardo
1 year ago
I'm a bit confused on the differences between the two options. I'll need to review my notes on Spring Beans and Java Delegates to make sure I understand the trade-offs before answering this.
CH
Cherelle
1 year ago
Okay, let's see. I think the key here is understanding when you'd want to use a Spring Bean versus a Java Delegate. Invoking the logic in multiple workflows seems like a good reason to use a Spring Bean.
SE
Serina
1 year ago
Hmm, this one seems tricky. I'll need to think through the differences between a Spring Bean and a Java Delegate to figure out the best approach.
EL
Elmer
1 year ago
D is key, who doesn't love a good old dependency injection? Makes life so much easier.
EV
Evette
1 year ago
B) To guarantee the implementation is only used from a Service Task
EV
Evette
1 year ago
D is definitely important for dependency injection.
TY
Tyra
1 year ago
Haha, E is like trying to sneak into the VIP section. Not happening, buddy!
TW
Twanna
1 year ago
B) To guarantee the implementation is only used from a Service Task
BR
Brynn
1 year ago
A) To invoke the business logic in more than just one workflow.
KA
Kate
1 year ago
B) To guarantee the implementation is only used from a Service Task
CA
Candra
1 year ago
A) To invoke the business logic in more than just one workflow.
CO
Cory
1 year ago
I'm not sure about C and D, but I think A and B are definitely important reasons.
CA
Carey
1 year ago
I agree with Cristina. A and B make sense for implementing business logic as a custom Spring Bean.
SU
Sue
1 year ago
C is a no-go, you don't want to mix business logic in a Script Task. Sticking to Service Tasks is the way to go.
LE
Leonard
1 year ago
B) To guarantee the implementation is only used from a Service Task
CH
Chandra
1 year ago
A) To invoke the business logic in more than just one workflow.
JU
Judy
1 year ago
A and D seem like the best options to me. Invoking the logic from multiple workflows and being able to inject dependencies are definitely useful.
AL
Alisha
1 year ago
Definitely, those are important factors to consider when deciding between a custom Spring Bean and a Java Delegate.
AL
Alisha
1 year ago
I agree, A and D are solid reasons for using a custom Spring Bean.
CR
Cristina
1 year ago
I think A and B are valid reasons.