Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IBM Exam C9510-401 Topic 8 Question 102 Discussion

Actual exam question for IBM's C9510-401 exam
Question #: 102
Topic #: 8
[All C9510-401 Questions]

A WebSphere Application Server cell was configured with a deployment manager node and a custom node. An operator manually changed some configuration files in the custom node, and the node became out of synch with the master repository.

The system administrator used the Synchronize button in the system administration session of the Integrated Solutions Console (ISC) to try to resynchronize the node, but the node remained out of sync.

What should the administrator do to fix it?

Show Suggested Answer Hide Answer
Suggested Answer: B

In WebSphere Application Server Version 6.1, a trust association interceptor (TAI) that uses the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) to securely negotiate and authenticate HTTP requests for secured resources was introduced. This function was deprecated In WebSphere Application Server 7.0. SPNEGO web authentication has taken its place to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method.

References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/csec_ssovo.html


Contribute your Thoughts:

Caitlin
3 months ago
Hey, at least the operator didn't accidentally delete the entire node. That would have been a real head-scratcher!
upvoted 0 times
...
Horace
3 months ago
Manually copying the config files? That's a lot of work, and I'm pretty sure the Full Resynchronize button is designed to handle this exact scenario.
upvoted 0 times
...
Zachary
3 months ago
Recreating the custom profile? That's a bold move, but I'm not convinced it's the best solution here. Let's try the Full Resynchronize first.
upvoted 0 times
Leeann
28 days ago
Let's go ahead and use the Full Resynchronize button to fix the synchronization issue.
upvoted 0 times
...
Kirby
29 days ago
I'm not sure about recreating the custom profile, let's go with the Full Resynchronize first.
upvoted 0 times
...
Margurite
1 months ago
I think using the Full Resynchronize button is the best course of action in this situation.
upvoted 0 times
...
Louisa
2 months ago
I agree, trying the Full Resynchronize button seems like a safer option.
upvoted 0 times
...
...
Brendan
3 months ago
Invoking the 'sync' operation on the NodeSync MBean? Sounds like a fun experiment, but I'm not sure it'll fix the issue.
upvoted 0 times
Kandis
2 months ago
C: Maybe recreating the custom profile could also work without deleting the node.
upvoted 0 times
...
Quinn
2 months ago
B: Yeah, that could help get everything back in sync.
upvoted 0 times
...
Orville
2 months ago
A: I think using the Full Resynchronize button might be the best option.
upvoted 0 times
...
...
Wenona
3 months ago
Ah, the age-old problem of manual configuration changes. Looks like the Full Resynchronize button is the way to go. That should put things back in sync.
upvoted 0 times
Willard
2 months ago
User 3: I've used that button before and it worked like a charm.
upvoted 0 times
...
Nichelle
2 months ago
User 2: Agreed, that should help get everything back in sync.
upvoted 0 times
...
Audra
3 months ago
User 1: I think using the Full Resynchronize button is the best option here.
upvoted 0 times
...
...
Selene
4 months ago
Hmm, that's a good point. Maybe we should consider both options and see which one works.
upvoted 0 times
...
Mirta
4 months ago
I disagree, I believe option B) Invoke ''sync'' operation on NodeSync MBean would be more effective.
upvoted 0 times
...
Selene
4 months ago
I think option A) Use the Full Resynchronize button is the best choice.
upvoted 0 times
...

Save Cancel