Question : Your company is involved in ecommerce business and they have partnership with one of the popular data analytics company, who provides various suggestions like advertisement recommendation, product recommendations etc. Hence, they request you to share your data as latest as possible with them. You are using Aurora DB as a backend database and your partner also have AWS accounts and they also run analytics on AWS infra. Which of the following is best suitable and correct?
1. You will give your partner access to one of the live replica in one of the availability zone based on their preference.
2. You will use automated snapshots creation and configure to be shared with the partner AWS account.
3. You will manually create a snapshot from live Aurora DB and then share that snapshot with the partner.
4. You cannot share Aurora DB snapshots with any other AWS account.
5. You will be creating VPC peering between your VPC (where Aurora DB hosted) and Partner VPC. So that partner can directly access the snapshots
Correct Answer : 3 Explanation: What question want? How do you share latest data with the partner, who also has AWS account, so that they can run analytics on that?
Remember: You should never ever give live data access to anybody not even developer, tester and data analytics team of your own organization. Hence, option 1, 5 is out.
Option 2 : You can have automated snapshots created. But they cannot be automatically shared with any other AWS account ID. Hence, this option is also out. Option 3 : Yes, you can create snapshot of your Aurora DB and share with any other account ID (it can be shared with up to 20 Account Id as of now). Hence, this is correct option.
Option 4: You can share snapshot with other AWS account. So this statement is altogether wrong.
Please note important points with regards to AuroraDB - Automated backups are always enabled on Amazon Aurora DB Instances. Backups do not impact database performance. - There is no performance impact when taking snapshots. Note that restoring data from DB Snapshots requires creating a new DB Instance. - Amazon Aurora automatically maintains 6 copies of your data across 3 Availability Zones and will automatically attempt to recover your database in a healthy AZ with no data loss. - In the unlikely event your data is unavailable within Amazon Aurora storage, you can restore from a DB Snapshot or perform a point-in-time restore operation to a new instance. - latest restorable time for a point-in-time restore operation can be up to 5 minutes in the past. - You can choose to create a final DB Snapshot when deleting your DB Instance. If you do, you can use this DB Snapshot to restore the deleted DB Instance at a later date. - Amazon Aurora retains this final user-created DB Snapshot along with all other manually created DB Snapshots after the DB Instance is deleted. Only DB Snapshots are retained after the DB Instance is deleted (i.e., automated backups created for point-in-time restore are not kept). - You can share a snapshot with a different AWS account, and the owner of the recipient account can use your snapshot to restore a DB that contains your data. - You can even choose to make your snapshots public - that is, anybody can restore a DB containing your (public) data. - You can use this feature to share data between your various environments (production, dev/test, staging, etc.) that have different AWS accounts, as well as keep backups of all your data secure in a separate account in case your main AWS account is ever compromised. - There is no charge for sharing snapshots between accounts. However, you may be charged for the snapshots themselves, as well as any databases you restore from shared snapshots. - AWS do not support sharing automatic DB snapshots. To share an automatic snapshot, you must manually create a copy of the snapshot, and then share the copy. - You can share your Aurora snapshots in all AWS regions where Aurora is available. - Very important: Your shared Aurora snapshots will only be accessible by accounts in the same region as the account that shares them. - you can share encrypted Aurora snapshots.
Question : Which of the following is true for Amazon Aurora DB? A. Aurora DB automatically divides databased in 10GB segments of each. B. It will create size copies of each segment across three availability zone C. If there is any data corruption occurred, you have to manually correct in each replica D. You have to write a process to scan all the data blocks for finding errors in it. 1. A,B 2. B,C 3. C,D 4. A,D 5. B,D
Correct Answer : 1 Explanation: AuroraDB is a managed service from the AWS, Hence most of the things should be available out of the box and need not to be done manually. For AuroraDB - Yes, it divide database in 10GB segment of each and will be copied across three availability zone. - Amazon can handle loss of data if two replica out of six are corrupted in case of write availability and three replica corrupted in case of read availability. - AuroaDB is a self-healing DB, so if any corruption found for storage, it will heal it and scans automatically to find errors.
Question : In your application you are using Aurora MySQL DB as a backend database, it is required that your application should not go down and its very critical application. Hence, you decided to replicate data across the region. Which of the following statement is correct for that scenario?
A. You cannot setup replication for Aurora MySQL DB across the region. B. You can setup replication for Aurora MySQL DB across region but it will have few milliseconds of lag with the primary DB. C. You cannot promote cross-region replica as a Primary RDS for your application D. You can promote cross-region Aurora DB as a primary but it will take few minutes to do that 1. A,B 2. B,C 3. C,D 4. A,D 5. B,D
Correct Answer : 5 Explanation: You can setup Aurora MYSQL DB across the region for replication. This replication is single threaded and depend on many other network factor, which can delay the replication. You can promote cross region replica as a Primary DB. However, promotion process will take few minutes depending on your workload.
Even you can set the priority which replica can be promoted in case of failure.
2. You will be writing an AWS Lambda function which will keep checking once in week age of particular object and take action accordingly.
3. You will have to setup bucket policy specifically for these two different storage one for Score card and another for certificate.
4. You will be using Simple Workflow service where in one activity you will check the age of certificate and move to RRS and in another activity you will check score card age and delete that object if those are older than one year. And schedule that workflow to run once in a week.