You deployed your company website using Elastic Beanstalk and you enabled log file rotation to S3. An Elastic
Map Reduce job is periodically analyzing the logs on S3 to build a usage dashboard that you share with your
CIO. You recently improved overall performance of the website using Cloud Front for dynamic content delivery
and your website as the origin.
After this architectural change, the usage dashboard shows that the traffic on your website dropped by an
order of magnitude. How do you fix your usage dashboard’?
A.
Enable Cloud Front to deliver access logs to S3 and use them as input of the Elastic Map Reduce job.
B.
Turn on Cloud Trail and use trail log tiles on S3 as input of the Elastic Map Reduce job
C.
Change your log collection process to use Cloud Watch ELB metrics as input of the Elastic Map Reduce job
D.
Use Elastic Beanstalk “Rebuild Environment” option to update log delivery to the Elastic Map Reduce job.
E.
Use Elastic Beanstalk ‘Restart App server(s)” option to update log delivery to the Elastic Map Reduce job.
Hi,
I would choose answer A
See also: http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/AccessLogs.html
Thx, Frank
A
A.
Enable Cloud Front to deliver access logs to S3 and use them as input of the Elastic Map Reduce job.
I choose A. Why some pass4sure site choose “Restart app server”?
A.
Enable Cloud Front to deliver access logs to S3 and use them as input of the Elastic Map Reduce job.
Choice is between D & E. Reason, this was a working system, but post deployment, there seems to be some issues with the application. Presuming all is well, only thing need to be done is restart.
D – Is a legitimate command
E is not a legitimate command
Hence D
A for sure.
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/AccessLogs.html#access-logs-choosing-s3-bucket
Re: D and E. The EMR job and CloudFront components would be configured independently from the ElasticBeanstalk environment. Since the necessary changes to add CloudFront logs into the S3 bucket for the EMR job to ingest and work on would be configured in CloudFront (not in the web or app servers, which never see the traffic CloudFront is handling for them), you should not have to touch your ElasticBeanstalk environment.
A
A