nerdexam
Amazon

SOA-C02 · Question #222

A company has an organization in AWS Organizations. The company uses shared VPCs to provide networking resources across accounts. A SysOps administrator has been able to successfully launch and…

The correct answer is A. Request an instance quota increase from the account that owns the VPC. Important note: The provided answer key appears to be incorrect. Based on how AWS actually works, C is the correct answer, not A. In a shared VPC (via AWS Resource Access Manager), EC2 instance quotas are enforced at the account level - instances launched by a participant…

Submitted by yuki_2020· Mar 30, 2026Monitoring, Logging, and Remediation

Question

A company has an organization in AWS Organizations. The company uses shared VPCs to provide networking resources across accounts. A SysOps administrator has been able to successfully launch and manage Amazon EC2 instances in a participant account. However the SysOps administrator is now receiving an InstanceLimitExceeded error when the SysOps administrator tries to launch a new EC2 instance. What should the SysOps administrator do to resolve this error?

Options

  • ARequest an instance quota increase from the account that owns the VPC
  • BLaunch additional EC2 instances in a different AWS Region
  • CRequest an instance quota increase from the parte pant account
  • DLaunch additional EC2 instances by using a different Amazon Machine image (AMI)

How the community answered

(32 responses)
  • A
    69% (22)
  • B
    19% (6)
  • C
    9% (3)
  • D
    3% (1)

Explanation

Important note: The provided answer key appears to be incorrect. Based on how AWS actually works, C is the correct answer, not A.

In a shared VPC (via AWS Resource Access Manager), EC2 instance quotas are enforced at the account level - instances launched by a participant account in a shared subnet count against the participant account's quota, not the VPC owner's. Therefore, when the SysOps administrator in the participant account hits InstanceLimitExceeded, they must request a quota increase for the participant account through AWS Service Quotas or AWS Support.

Option A (request from the VPC owner) is wrong because the VPC owner's quotas are unaffected by instances the participant launches - quota enforcement is always per-account. Option B (different region) would technically create new capacity, but it dodges the real issue and isn't a fix - it just moves the work somewhere else. Option D (different AMI) has no effect on instance limits whatsoever; the AMI only determines the OS/software image, not quota consumption.

Memory tip: Think "who owns the instance, pays the quota." The participant account owns the EC2 instances it launches (even in a shared subnet), so the participant account's quota is what gets consumed and what needs to be raised.


If this question appeared on an official AWS practice exam, it may contain an error in the answer key, or there is a very specific scenario the question is describing that differs from standard shared VPC behavior. I'd recommend verifying against AWS documentation before trusting answer key A.

Topics

#EC2#Service Quotas#Shared VPC#AWS Organizations

Community Discussion

No community discussion yet for this question.

Full SOA-C02 Practice