An on-premises environment needs a consistent-bandwidth connection to AWS without sending traffic over the public internet.
Add encryption if the requirement calls for it.
Choose TWO appropriate statements.
Direct Connect provides a dedicated connection, while VPN can be layered on it when traffic encryption is required.
Detailed explanation
Direct Connect itself does not encrypt traffic, so a VPN can provide the additional encryption layer.
Direct Connect itself does not encrypt traffic, so a VPN can provide the additional encryption layer.
Private DNS provides name resolution and does not create a network circuit.
Private DNS provides name resolution and does not create a network circuit.
Public exposure does not provide a dedicated path or the stated connectivity characteristics.
Public exposure does not provide a dedicated path or the stated connectivity characteristics.
Direct Connect connects an on-premises location to AWS over a dedicated path.
Direct Connect connects an on-premises location to AWS over a dedicated path.
Check official documentation
Compare the following points with the official documentation.
AWS Direct ConnectとAWS Site-to-Site VPNの公式説明を確認する。
What to confirm
専用接続と暗号化の要件をDirect ConnectとVPNへ分けて設計できる。
Key points
- AWS Direct Connect
- VPN
- Dedicated connection
- Encryption
Notes
- Environment: AWS公式Direct Connect・VPNドキュメントの確認
- Confirm current AWS service behavior and architecture guidance in the official documentation.
Foundation review
Separate requirements
Direct Connect addresses path characteristics; a VPN addresses encryption when that is additionally required.
DNS versus connectivity
A private hosted zone resolves names but does not provide a circuit or tunnel.