ETExamTower
Sign in
Q57Design Cost-Optimized Architectures

A company operates database workloads on AWS as the backend for its customer portals. The company uses a Multi-AZ database cluster on Amazon RDS for PostgreSQL. The company must implement a 30-day backup retention policy. It currently has both automated RDS backups and manual RDS backups. The company wants to retain both types of existing RDS backups that are less than 30 days old. Which solution will meet these requirements in the MOST cost-effective manner?

← → navigate · a answer
Community votes
C
75% (3)
D
25% (1)
A
0% (0)
B
0% (0)
Discussion · 5
C 11
This is C, you are looking for the most cost effective solution. Again if any of you use ChatGPT it will say A because it makes the most sense for automation and less management. But it is not the most cost effective. AWS Backup costs extra money. So A, is not correct. It is C.
C 5
A - AWS Backup is not required for configuring automated backup retention on RDS. It's native to the RDS service. So not using that will save us a fortune. B - Disabling backups and then re-enabling a 30-day retention policy? I don't get it C - Manual deletion will add operational tasks for sure, but in this case, it's actually reasonable and acceptable. D - Even sounds more absurd than B, because using AWS CloudFormation to automate deletion adds extra complexity.
2
Agree! Additionally we can configure RDS backup easily for a built-in 30 days retention, which meets the requirement and less cost than using AWS backup service
D 2
D makes more sense, since AWS CF will keep last 30 days from now on.
1
.respuesta correcta A-D : Para cumplir con los requisitos de etiquetado de instancias de Amazon EC2 con sensibilidad de datos y garantizar que las identidades de IAM no puedan eliminar una etiqueta o crear instancias sin una etiqueta, la combinación de pasos más adecuada es: A. En Organizaciones, cree una nueva política de etiqueta que especifique la clave de etiqueta de sensibilidad de datos y los valores requeridos. Aplica los valores de etiqueta para las instancias de EC2. Adjunte la política de etiquetas a la OU apropiada. D. Cree una política de control de servicio (SCP) para denegar la creación de instancias cuando no se especifica una clave de etiqueta. Crea otro SCP que evite que las identidades eliminen las etiquetas. Adjunte los SCP a la OU apropiada.