DVA-C02 Development with AWS Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The bucket policy denies access to the error.html object.

  Why it's wrong here

  While a bucket policy can indeed deny access to specific objects, resulting in a 403 Forbidden error, this option is incorrect because the primary issue described is the failure to display a *custom* error page. If the bucket policy explicitly denied access to `error.html`, S3 would return a generic 403 error, not necessarily indicate a problem with the static website hosting configuration's ability to route to a custom error document. The question implies the custom error page mechanism itself is not functioning as expected, which points to configuration rather than a direct access denial.

• ✓

  The Error document field in the static website hosting configuration is not set to error.html.

  Why this is correct

  This is the correct answer because the 'Error document' field within the S3 static website hosting configuration explicitly tells S3 which HTML file to serve when a 4xx error occurs. Without this field being correctly set to `error.html`, S3 will not know to redirect error requests to your custom page, even if `error.html` exists and has appropriate permissions. This configuration acts as the crucial routing instruction for custom error handling, ensuring a branded user experience during errors.

• ✗

  The index.html is missing from the bucket.

  Why it's wrong here

  This option is incorrect because the absence of `index.html` would typically result in an HTTP 404 Not Found error when a user attempts to access the root URL or a directory without a specified index document. A 403 Forbidden error, which is often the context for issues with custom error pages not displaying, indicates a permissions problem or an explicit denial of access, not that the requested resource itself is missing from the bucket. The type of error (403 vs. 404) is distinct.

• ✗

  The error.html object has incorrect permissions.

  Why it's wrong here

  Although `error.html` must ultimately be accessible for S3 to serve it (typically via a public read bucket policy), incorrect individual object permissions are not the most direct cause for the *custom error page not being displayed* by the static website hosting feature. If permissions were the sole issue, S3 would likely return a generic 403 Forbidden error, indicating a direct access problem. The failure of the custom error page mechanism to even attempt to route to `error.html` points more strongly to a missing or incorrect configuration in the static website hosting settings, rather than just the object's permissions.