nerdexam
Amazon

SOA-C02 · Question #231

A company is using Amazon CloudFront to serve static content for its web application to its users. The CloudFront distribution uses an existing on-premises website as a custom origin. The company…

The correct answer is A. Examine the expiration date on the certificate on the origin site. HTTP 502 errors from CloudFront can occur because of the following reasons: There's an SSL negotiation failure because the origin is using SSL/TLS protocols and ciphers that aren't supported by CloudFront. There's an SSL negotiation failure because the SSL certificate on the…

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

Question

A company is using Amazon CloudFront to serve static content for its web application to its users. The CloudFront distribution uses an existing on-premises website as a custom origin. The company requires the use of TLS between CloudFront and the origin server. This configuration has worked as expected for several months. However, users are now experiencing HTTP 502 (Bad Gateway) errors when they view webpages that include content from the CloudFront distribution. What should a SysOps administrator do to resolve this problem?

Options

  • AExamine the expiration date on the certificate on the origin site.
  • BExamine the hostname on the certificate on the origin site.
  • CExamine the firewall rules that are associated with the origin server.
  • DExamine the network ACL rules that are associated with the CloudFront distribution.

How the community answered

(44 responses)
  • A
    80% (35)
  • B
    5% (2)
  • C
    2% (1)
  • D
    14% (6)

Explanation

HTTP 502 errors from CloudFront can occur because of the following reasons: There's an SSL negotiation failure because the origin is using SSL/TLS protocols and ciphers that aren't supported by CloudFront. There's an SSL negotiation failure because the SSL certificate on the origin is expired or invalid, or because the certificate chain is invalid. There's a host header mismatch in the SSL negotiation between your CloudFront distribution and the custom origin. The custom origin isn't responding on the ports specified in the origin settings of the CloudFront The custom origin is ending the connection to CloudFront too quickly. https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cloudfront-connection-error/

Topics

#CloudFront 502 error#TLS certificate expiration#custom origin HTTPS#distribution troubleshooting

Community Discussion

No community discussion yet for this question.

Full SOA-C02 Practice