Exam AWS-SysOps topic 1 question 761 discussion

CE Scaling in/out and Changing node types is possible with Memcached Refer to https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/Scaling.html

Option C, adding additional worker nodes to the ElastiCache cluster, increases the capacity and distributes the workload across more nodes. This can help alleviate high CPU utilization by allowing the cluster to handle the increased load more efficiently. Option E, vertically scaling the ElastiCache cluster by changing the node type, involves upgrading the node type to a more powerful instance. This provides increased CPU and memory resources, which can help improve the performance and handle higher workloads.

C and E are the answers

C | E are the answers

Scaling Memcached Horizontally: The Memcached engine supports partitioning your data across multiple nodes. Because of this, Memcached clusters scale horizontally easily. A Memcached cluster can have from 1 to 20 nodes. To horizontally scale your Memcached cluster, merely add or remove nodes. Scaling Memcached Vertically: Scale vertically by using a different node type. When you scale your Memcached cluster up or down, you must create a new cluster. Memcached clusters always start out empty unless your application populates it. CORRECT: "Add additional nodes to the existing ElastiCache cluster" is the correct answer. CORRECT: "Vertically scale the ElastiCache cluster by changing the node type" is also a correct answer.

C. Add additional worker nodes to the ElastiCache cluster E. Vertically scale the ElastiCache cluster by changing the node type

I'll go with C,E

CE Memcached When you reach 90% CPU on a Memcached node, you’ll need to scale up your cluster. You can do this by adding new cache nodes, or by scaling the node to a more powerful instance type. These actions can be performed either in the AWS Console or by using the AWS CLI.

C. Add additional worker nodes to the ElastiCache cluster E. Vertically scale the ElastiCache cluster by changing the node type

ill go with C and E :

Answer C. Adding nodes to a Memcached cluster increases the number of you cluster's partitions. When you change the number of partitions in a cluster some of your key spaces need to be remapped so that they are mapped to the right node. Remapping key spaces temporarily increases the number of cache misses on the cluster Answer E. Scaling Memcached Vertically - When you scale your Memcached cluster up or down, you must create a new cluster. Memcached clusters always start out empty unless your application populates it.

ill go with C and E : This is a host-level metric reported as a percent. For more information, see Host-Level Metrics. Because Memcached is multi-threaded, this metric can be as high as 90%. If you exceed this threshold, scale your cache cluster up by using a larger cache node type, or scale out by adding more cache nodes.

it's C & E

A & C are correct (Horizontal scaling) not vertical scaling

Answer: C,E High CPU Utilization "Because Memcached is multi-threaded, this metric can be as high as 90%. If you exceed this threshold, scale your cache cluster up by using a larger cache node type, or scale out by adding more cache nodes"

C. Add additional worker nodes to the ElastiCache cluster E. Vertically scale the ElastiCache cluster by changing the node type https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/Scaling.html