Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
AWS Service Catalog permite definir plantillas preaprobadas para lanzar EMR clusters con configuraciones controladas (versiones, aplicaciones, seguridad). Se pueden definir permisos por rol (por persona o grupo de IAM) para controlar qué acciones puede realizar cada usuario. Se pueden forzar políticas de etiquetado obligatorio mediante plantillas y restricciones de uso. Garantiza el principio de menor privilegio, ya que los usuarios no tienen acceso completo a EMR sino sólo a lo autorizado por Service Catalog. Ideal para ambientes empresariales donde se necesita control centralizado, gobernanza y cumplimiento
Using AWS Service Catalog (Option C) to control the Amazon EMR versions available for deployment, the cluster configuration, and the permissions for each user persona meets all the requirements: It provides a centralized management interface for IT services It allows you to define and enforce policies for resource provisioning and access control It enables you to manage multiple instances of an application (in this case, EMR clusters) from a single console
Why not Option A is because it involves creating IAM roles and attaching identity-based policies, which is solid. But it relies on AWS Config rules to ensure compliance, which adds an extra layer of management and potential lag in remediation. AWS Service Catalog, on the other hand, simplifies control over EMR versions, configurations, and permissions, and it also enforces resource tagging directly during deployment, making it more efficient and streamlined for managing access and compliance.