- Barajar
ActivarDesactivar
- Alphabetizar
ActivarDesactivar
- Frente Primero
ActivarDesactivar
- Ambos lados
ActivarDesactivar
- Leer
ActivarDesactivar
Leyendo...
Cómo estudiar sus tarjetas
Teclas de Derecha/Izquierda: Navegar entre tarjetas.tecla derechatecla izquierda
Teclas Arriba/Abajo: Colvea la carta entre frente y dorso.tecla abajotecla arriba
Tecla H: Muestra pista (3er lado).tecla h
Tecla N: Lea el texto en voz.tecla n
Boton play
Boton play
11 Cartas en este set
- Frente
- Atrás
|
Differences between Launch template and LAunch Configuration
|
Launch Template is newer
Is possible save Network config Launch Configuration is older Is noy possible save networking config. |
|
What include a Launch template?
|
*AMI
*EC2-instance size *SEcurity groups *Posible network info. |
|
Auto Scaling is vital to create a _____________ application
|
Highly Available
|
|
Remember to select answer that spread resources out over multiple AZ and utilize load balancer
|
recuerde seleccionar la respuesta que distribuya los recursos en múltiples AZ y utilice el balanceador de carga
|
|
If the database have Read-heavy workload
|
Use Read replicas to solve it
|
|
RDS scale up and sale down?
|
No, only scale up.
|
|
Is good idea multi-AZ in RDS
|
Yes, it's a good idea but is necessary turn on. Only if is dev is not good choice.
|
|
If we have RDS vs Aurora
|
Aurora is best choice.
|
|
In DynamoDB questions what is better performance or price?
|
Price
|
|
What use if we have a predictable workload?
What use if we have a sporadic workload? |
Provisioned capacity.
On-demand capacity. |
|
how work the default termination policy in auto scaling group?
|
When Amazon EC2 Auto Scaling terminates instances, it first determines which Availability Zones have the most instances, and it finds at least one instance that is not protected from scale in.
1 Determine whether any of the instances eligible for termination use the oldest launch template or launch configuration 2 After applying the preceding criteria, if there are multiple unprotected instances to terminate, determine which instances are closest to the next billing hour. If there are multiple unprotected instances closest to the next billing hour, terminate one of these instances at random Note: that terminating the instance closest to the next billing hour helps you maximize the use of your instances that have an hourly charge |
