which of the following features in a cost effective and efficient manner?

Refer to the architecture diagram above of a batch processing solution using Simple Queue Service (SOS) to set
up a message queue between EC2 instances which are used as batch processors Cloud Watch monitors the
number of Job requests (queued messages) and an Auto Scaling group adds or deletes batch servers
automatically based on parameters set in Cloud Watch alarms. You can use this architecture to implement
which of the following features in a cost effective and efficient manner?

Refer to the architecture diagram above of a batch processing solution using Simple Queue Service (SOS) to set
up a message queue between EC2 instances which are used as batch processors Cloud Watch monitors the
number of Job requests (queued messages) and an Auto Scaling group adds or deletes batch servers
automatically based on parameters set in Cloud Watch alarms. You can use this architecture to implement
which of the following features in a cost effective and efficient manner?

A.
Reduce the overall lime for executing jobs through parallel processing by allowing a busy EC2 instance that
receives a message to pass it to the next instance in a daisy-chain setup.

B.
Implement fault tolerance against EC2 instance failure since messages would remain in SQS and worn can
continue with recovery of EC2 instances implement fault tolerance against SQS failure by backing up messages
to S3.

C.
Implement message passing between EC2 instances within a batch by exchanging messages through SOS.

D.
Coordinate number of EC2 instances with number of job requests automatically thus Improving cost
effectiveness.

E.
Handle high priority jobs before lower priority jobs by assigning a priority metadata field to SQS messages.



Leave a Reply 10

Your email address will not be published. Required fields are marked *


Frank

Frank

Hi,

I think the answer should be D, because of the “cost effective and efficient” in the question. And SQS is already a reliable, highly scalable hosted queue service, so backup to S3 is not necessary.

Any thoughts are welcome.

Thanks,
Frank

fun4two

fun4two

answer is d

muthu

muthu

Yes. A is correct.

Amazon EC2 allows applications to scale up and down dynamically, application developers can easily vary the number of compute instances based on the amount of work in the SQS queues, to ensure that jobs are executed in a timely manner.

Tsao

Tsao

“Daisy-chain” setup makes it 100% wrong.

Manu

Manu

I think the answer is D

dat

dat

I think answer is D.

pacosoplas

pacosoplas

D
With clodWatch check how is the queue, and the you can start or stop EC2 instance, so low cost and hight efficient.