Question 176:
HikeHills.com (HH) is an online specialty retailer that sells clothing and outdoor refreshment gear for trekking, go camping, boulevard biking, mountain biking, rock hiking, ice mountaineering, skiing, avalanche protection, snowboarding, fly fishing, kayaking, rafting, road and trace running, and many more. HHruns their entire online infrastructure on java based web applications running on AWS. The HH is capturing click stream data and use custom-build recommendation engine to recommend products which eventually improve sales, understand customer preferences and already using AWS kinesis KPL to collect events and transaction logs and process the stream. HHIT team identified lot of performance issues with the Kinesis Stream and based on the metrics captured, identified hot and cold shards. IT team wants to effectively remove the unused capacity. There are 3 shards SHARD 1 with a hash key range of 276...381, SHARD 2 with a hash key range of 382...454 and SHARD 3 with a hash key range of 455...510. Shard 1 and Shard 3 are cold shards while Shard 2 is a hot shard. What re-sharding strategy needs to be applied and how can it be applied?
Answer options:
A.DELETE SHARD 1, SHARD 3 use only SHARD 2 B.DELETE SHARD 1, SHARD 2, SHARD 3, redesign the SHARDING strategy C.MERGE SHARD 1, SHARD2 and SHARD3 into 1 and split shards into 2 shards, SHARD123A with hash keys 276…420, SHARD123B as 425....510 D.MERGE 3 SHARDS into 1 SHARD with hash keys between 276..510 which remove unused capacity.