A CloudOps engineer has created an AWS Service Catalog portfolio and shared it with a second AWS account in the company, managed by a different CloudOps engineer. Which action can the CloudOps enginee

Question

Options

• AAdd a product from the imported portfolio to a local portfolio.
• BAdd new products to the imported portfolio.
• CChange the launch role for the products contained in the imported portfolio.
• DCustomize the products in the imported portfolio.

• A
  77% (34)
• B
  11% (5)
• C
  5% (2)
• D
  7% (3)

Explanation

Per the AWS Cloud Operations and Service Catalog documentation, when a portfolio is shared across AWS accounts, the recipient account imports the shared portfolio. The recipient CloudOps engineer cannot modify the original products or their configurations but Add products from the imported portfolio into their local portfolios for deployment, Control end-user access in the recipient account, and Manage local constraints or permissions. However, the recipient cannot edit, delete, or reconfigure the shared products (Options B, C, and D). The source (owner) account retains full administrative control over products, launch roles, and lifecycle policies. This model aligns with AWS CloudOps principles of centralized governance with distributed self- service deployment across multiple accounts. Thus, Option A is correct--imported portfolios allow the recipient to add products to a local portfolio but not alter the shared configuration.

No community discussion yet for this question.