MENU
Which service-orientation principle would be used to justify a corporate policy that limits or restricts access to technical specifications that show design and technology details about the underlying implementation of a published service? Select the correct answer.
Suggested Answer: D
Get Premium S90.03 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
GL
Glenn
10 months ago
Surprised this is even a question! Seems obvious to me.
VI
Vi
10 months ago
Totally agree with that! Keeps the implementation hidden.
LA
Lashandra
11 months ago
Wait, isn't it more about C? Service Autonomy?
JE
Jesusita
11 months ago
I don't know, I feel like A could fit too.
VI
Vincenza
11 months ago
I think it's definitely D, Service Abstraction.
VE
Verlene
11 months ago
I thought Service Abstraction was about hiding complexity, but I'm not confident if that's the right answer here. What if it's actually Service Statelessness?
JU
Justine
11 months ago
I feel like this question is similar to one we practiced on service design principles, but I can't recall the exact term. Could it be Service Discoverability?
BE
Bettye
12 months ago
I'm not entirely sure, but I remember something about how limiting access can help maintain service integrity. Maybe it's Service Autonomy?
DE
Deeanna
12 months ago
I think the principle we're looking for is related to hiding implementation details, which sounds like it could be Service Abstraction.
CH
Chaya
1 year ago
I'm pretty confident the answer is D, Service Abstraction. That principle is all about encapsulating the underlying technology and only exposing the service interface, which aligns with the scenario described in the question.
KE
Kenny
1 year ago
Okay, I've got it. The answer is D, Service Abstraction. This principle is about hiding the internal implementation details of a service, which is what the question is asking about.
TA
Tayna
1 year ago
Hmm, I'm a bit unsure about this one. I know the service-orientation principles, but I'm not sure which one specifically would apply to limiting access to technical specs. Let me think this through...
JA
Jamey
1 year ago
I think this is asking about the service-orientation principle that would justify restricting access to technical details. The key seems to be "service abstraction", which hides the underlying implementation.
BL
Blondell
1 year ago
I'm gonna have to go with service abstraction on this one. Gotta keep those implementation secrets under lock and key!
GO
Goldie
1 year ago
Agreed, it's all about protecting the underlying implementation.
EL
Ellen
1 year ago
Definitely, it helps maintain the independence of the service.
LU
Lucina
1 year ago
Yeah, it's important to keep those details hidden from users.
VE
Velda
1 year ago
I think service abstraction makes sense in this case.
JA
Janae
1 year ago
Haha, good luck trying to get any IT guy to give up their precious technical details! Service autonomy all the way.
TI
Timothy
1 year ago
True, but service autonomy ensures that the service has control over its own functionality and data, which is crucial in this scenario.
LO
Lonny
1 year ago
But wouldn't service abstraction also be important in this case to hide the complexity of the underlying implementation?
DO
Donte
1 year ago
I agree, service autonomy is key when it comes to protecting those technical details.
TE
Tess
1 year ago
Definitely, we need to limit access to certain details for security reasons.
PE
Peggie
1 year ago
I agree, service autonomy is key in protecting sensitive information.
TH
Thaddeus
1 year ago
I see where you're coming from, Tashia, but I still think D) Service Abstraction is the best choice.
TA
Tashia
1 year ago
I'm not sure, but I think C) Service Autonomy could also be a valid option.
NI
Nichelle
1 year ago
Service discoverability is important, but in this case, restricting access to the technical specs is more about service abstraction, isn't it?
IS
Isadora
1 year ago
Service discoverability is important, but in this case, service abstraction seems to be the main principle at play.
VI
Vincenza
1 year ago
That's a good point, service autonomy does play a role in controlling access to certain information.
AN
Antonette
1 year ago
I think service autonomy could also be a factor in limiting access to technical specifications.
FR
Freeman
1 year ago
Yes, you're right. It's all about service abstraction.
SY
Sylvia
1 year ago
I think service abstraction makes the most sense here. Hiding the implementation details helps protect the service's autonomy.
MI
Micaela
1 year ago
Service abstraction definitely makes sense in this scenario to hide the implementation details.
KA
Karan
1 year ago
I think service autonomy is the best choice to limit access to technical specifications.
KA
Katie
1 year ago
I agree, service abstraction would help protect the service's autonomy.
VO
Von
1 year ago
I agree with Cyril. Service Abstraction makes sense in this scenario.
CY
Cyril
1 year ago
I think the answer is D) Service Abstraction.