When synchronizing clusters, which of the following statements is NOT true?
A.
The state of connections using resources is maintained by a Security Server, so these connections cannot be synchronized.
B.
In the case of a failover, accounting information on the failed member may be lost despite a properly working synchronization.
C.
Only cluster members running on the same OS platform can be synchronized.
D.
Client Authentication or Session Authentication connections through a cluster member will be lost if the cluster member fails.
Correct answer is B
in document clusterxl admin guide
The reason for these restrictions is that user authentication state is maintained on Security Servers,
which are processes, and thus cannot be synchronized on different machines in the way that kernel data
can be synchronized. However, the state of session authentication and client authentication is stored in
kernel tables, and thus can be synchronized.
The state of connections using resources is maintained in a Security Server, so these connections
cannot be synchronized for the same reason that user-authenticated connections cannot be
synchronized
0
0
Sorry but the correct answer is still D since:
– Accounting information is accumulated in each cluster member and reported separately to the Security Management server, where the information is aggregated. In case of a failover, accounting information that was accumulated on the failed member but not yet reported to the Security Management server is
lost.
0
0
Correct Answer is D.
Only USER Authentication connections are lost during a failover.
Page 163 Section 3 of the R70 CCSE Courseware manual.
3. A User Authenticated connection through a cluster member will be lost if the cluster member fails. Other synchronized cluster members will be unable to resume the connection. Howerver, a Client Authenticated or Session Authenticated connecdtion will not be lost.
0
0
It’s interesting to compare this question against question nr. 237 🙂
0
0