Question : You are working with a Bank as a solution architect, to develop their mobile wallet applications and you decide to use all transactions will be stored in Amazon RDS with Multi-AZ deployment. Entire application has been productionized and CloudWatch alarm has been created, which send monitoring detail (only critical) to your mobile using SNS (simple notification service). One night you got an alert that your primary RDS instance has gone down. What is your immediate step to move to secondary DB instance?
1. You immediately contact your production support team, they might have got same alert and ask them to change the DNS entry so that application can point to secondary DB instance.
2. Ask application developer team to change the configuration file where database connection string is configured.
4. You must monitor the application and RDS. Because of primary failure anything wrong happen.
Correct Answer : Get Lastest Questions and Answer : Explanation: Practically, you should have done nothing in this scenario on immediate basis. Only you should monitor this environment. Because, no changes is required, that is the feature of using RDS you will get. It will behind the scene automatically point the new DB instance and keep monitoring your environment.
Question : You are having SQL Server enterprise edition, to run your in-house HR application on that. However, you get to know that your only DBA is leaving the organization and on notice period will 30 days and he suggested, he will help you to have some solution where you can run your application without DBA for some time until you hire new one. And he suggested to moving database solution to AWS managed service AWS RDS. What is the correct statement for given scenario?
1. DBA will launch AWS RDS instance and install SQL server (Enterprise edition on it). You will be using your own license using BYOD model.
2. DBA will launch AWS RDS instance and install SQL server (Enterprise edition on it) and you will be using the RDS instance where license is already included in cost. So you don’t have to have explicit license purchased.
4. DBA will create SQL Server free edition RDS instance, so that he can save the hug licensing cost.
Correct Answer : Get Lastest Questions and Answer : Explanation: In given scenario, DBA left. Hence, you need managed solution, so certainly AWS RDS is a good choice. For SQL Server Enterprise edition there is no RDS instances which include license in it. You have to have your own license, so it will work on BYOL model (Bring your own license).
Question : You are implementing a website solution for an existing website, who had a hosting with the hosting provider and having a web server and a database server in backend. However, you need to migrate this website to AWS, which can provide high availability and resiliency for both the web server and database server. Hence, you decided to have at least 2 web server public facing and 2 db server in highly protected. How many subnet you should have created to have for the given scenario?
1. You will be having one subnet only in AWS and configure security and NACL for the DB server.
2. You will be having two subnet one public facing for web server and one private for D
4. You will be having eight subnet four public facing for web server and four private for DB
Correct Answer : Get Lastest Questions and Answer : Explanation: By reading the scenario, what you conclude - You need High Availability and resiliency - You need two webserver and two DB server For High Availability and resiliency, you should always consider across multi-AZ deployment solution. Always keep the server in separate subnet based on their responsibility. Hence, here we have two separate responsibility. It means at least 2 subnet. But for high availability and resiliency it should be in different AZ as well. However, as we know. Same subnet cannot be across two AZ, they are limited in same AZ. Hence, we need to have separate subnet in different AZ. Which lead us to have 4 subnets. 2 for Web Server and 2 for DB server in two AZ.
1. Run the bastion on two instances one in each AZ 2. Run the bastion on an active Instance in one AZ and have an AMI ready to boot up in the event of failure