Question-: Dynamic snitch monitor read latencies to avoid reading from hosts that have slowed down? A. True B. False
Answer: A
Explanation: Yes, Dynamic snitch can be used to monitor the read latencies to avoid reading from hosts that have slowed down.
Question-: You are bootstrapping a new node to Cassandra cluster. Which of the following parameters can help in defining number of tokens would be handled by this new node? A. v_token_count B. num_tokens C. initial_tokens D. additional_tokens
Answer: B
Explanation: Such type of questions are less asked in the exam. Because remembering the parameters are difficult. However, there are some common parameters which are used for the configuration on regular basis or discussed frequently. Hence, you should remember those common once. And num_tokens is such parameter. num_tokens define the amount of virtual nodes (tokens) the joining node will be assigned during bootstrap. In the Cassandra cluster default token allocation algorithm for the new node will pick num_tokens which would be random and this new node would be responsible for. Load distribution improves with a higher amount of virtual nodes, but it also increases token management overhead. The default of 256 virtual nodes should provide a reasonable load balance with acceptable overhead.
Question-: If you are restoring a node and want to have the previous tokens it was handling should remain same after restore. Then what is the option from below you would choose? A. v_token_count B. num_tokens C. initial_tokens D. additional_tokens
Answer: C
Explanation: We can assign the comma separated list of tokens manually with the initial_token values in Cassandra.yaml file. And in this case Cassandra will not do token assignment and skip the token allocation process. This may be useful when doing token assignment with an external tool or when restoring node with its previous tokens.