The correct options are Special Interest Groups concentrate on particular technical components like networking storage and scheduling and Working Groups coordinate initiatives that span multiple Special Interest Groups or that affect the entire project.

Special Interest Groups concentrate on particular technical components like networking storage and scheduling are focused teams that organize contributors around a specific area of the code base or ecosystem. They drive the technical design API changes implementation and ongoing maintenance for that component and they coordinate SIG-level meetings and subproject work.

Working Groups coordinate initiatives that span multiple Special Interest Groups or that affect the entire project handle cross cutting efforts that require collaboration across multiple SIGs or that touch project wide processes. Working groups are often temporary or chartered to address a broad initiative such as release tooling security audits or multi SIG feature work and they emphasize coordination rather than being the primary code owner for a single component.

A Special Interest Group is primarily a documentation resource that publishes procedural guides for contributors is incorrect because SIGs are not limited to documentation. SIGs own technical design and implementation for specific areas and they may produce documentation as part of that work but documentation is not their sole or primary role.

Working Groups maintain code and manage day to day merges for a single component is incorrect because working groups focus on cross SIG coordination and project wide initiatives. Day to day code maintenance and merges for a single component are typically handled by the SIG that owns that component.

Full AWS Practitioner Certification Question