MENU
Which of the following approaches represents a valid means of utilizing generic security logic?
Suggested Answer: D
Get Premium S90.18 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
CO
Cortney
10 months ago
Wait, can we really trust all those methods equally?
CE
Celeste
11 months ago
Totally agree with B, reuse is key!
RE
Rebbeca
11 months ago
All of the above seems too broad, right?
JA
Jacquelyne
11 months ago
I think C is the best option for flexibility!
TA
Tammi
11 months ago
A is solid, but B has its perks too.
TA
Tatum
11 months ago
I’m leaning towards D, thinking that all the approaches could be valid depending on the context. But I wish I had reviewed more examples before the exam!
KI
Kimbery
12 months ago
I feel like option C about using a service agent could be valid too, especially since it responds to runtime events. But I'm a bit confused about the differences between all these options.
BU
Buddy
12 months ago
I think abstracting security logic into a separate utility service was mentioned in a practice question. It seems like a good way to promote reuse.
AD
Adrianna
1 year ago
I remember discussing how embedding security logic within a service can help with consistency, but I'm not sure if it's the best approach overall.
HI
Hildegarde
1 year ago
I'm pretty confident that the correct answer is D - all of the above. Each of these approaches has its own merits, and the best solution may depend on the specific requirements and constraints of the system. I'll make sure to carefully consider the tradeoffs of each approach.
FE
Felicidad
1 year ago
Ah, I see. Abstracting the security logic into a service agent is an interesting approach. That would allow for reuse and the ability to execute the security logic in response to runtime events. I like that idea - it seems like a good balance between flexibility and consistency.
SA
Sabra
1 year ago
Hmm, I'm a bit unsure about this one. I'm not sure if embedding the security logic directly within the service is the best idea, as that could make it harder to update or change the security logic in the future. I'll have to think this through a bit more.
LE
Leota
1 year ago
I think the best approach here is to abstract the generic security logic into a separate utility service. That way, it can be reused across multiple services, which seems like the most efficient and maintainable solution.
EN
Ena
1 year ago
I'm a bit confused here. None of these options seem like a clear-cut example of a key component of regulated PII. I'll have to review my notes and try to eliminate the less relevant choices.
KE
Kenny
1 year ago
This question seems pretty straightforward. I think the answer is B - a place to store custom workflow scripts, jars, and custom lists of values for use in custom workflow.
EL
Eleni
1 year ago
This question seems a bit tricky, but I think I can figure it out. I'll need to carefully read through the options and think about how to properly set up the landed costs.
AL
Alpha
2 years ago
I personally think option D is the way to go, as it combines the benefits of both A and C for maximum security.
GE
Gerald
2 years ago
That's a good point, option C does offer more flexibility in terms of when the security logic is executed.
BR
Brock
2 years ago
All of the above? What is this, a buffet? I'm going with option B. Keep it simple, keep it secure.
RE
Rebbecca
2 years ago
I'm going to stick with option B. Keeping it simple and secure sounds good to me.
RU
Ruthann
2 years ago
I'm with User2 on this one. Option A it is.
JU
Jutta
2 years ago
I agree with User1. Option A seems like a solid choice.
MA
Marya
2 years ago
I think option A is the way to go. Embedding security logic within the service makes sense.
MA
Marica
2 years ago
I disagree, I believe option C is the most effective as it allows for reuse and execution in response to runtime events.
AN
Anabel
2 years ago
Hmm, I'm leaning towards option C. Having the security logic in a service agent that can respond to runtime events sounds pretty slick.
EZ
Ezekiel
2 years ago
Yeah, it definitely allows for reuse and can respond quickly to runtime events.
PA
Paola
2 years ago
I agree, having the security logic in a service agent seems like a flexible approach.
LE
Leatha
2 years ago
Option D, huh? Trying to cover all the bases, eh? Might as well throw in a dancing security guard for good measure.
HA
Halina
2 years ago
C) When required, generic security logic can be abstracted into a service agent. This allows for reuse and the security logic can be executed in response to runtime events.
PR
Providencia
2 years ago
B) When required, generic security logic can be abstracted into a separate utility service. This allows for reuse.
YV
Yvette
2 years ago
A) When required, generic security logic can be embedded within a service. The close proximity to the service logic maximizes the chances that the security logic will be consistently executed without interference from attackers.
GE
Gerald
2 years ago
I think option A is the best approach because embedding security logic within a service ensures consistent execution.
PO
Pok
2 years ago
Option B seems the most logical choice. Separating the security logic into a reusable utility service makes a lot of sense to me.
RI
Rickie
2 years ago
Having a service agent for security logic execution based on runtime events sounds efficient.
YU
Yuonne
2 years ago
It definitely makes sense to abstract security logic for reuse.
DE
Delisa
2 years ago
I think having a separate utility service for security logic is a good idea.
JO
Johnna
2 years ago
I agree, option B does seem like a practical approach.