The correct answer is to set the Secure and HttpOnly flags on the session cookie. The Secure flag ensures the cookie is transmitted only over HTTPS, preventing interception during man-in-the-middle attacks, while the HttpOnly flag blocks client-side scripts like JavaScript from accessing the cookie, directly mitigating cross-site scripting (XSS)-based session hijacking. On the AWS Certified Developer Associate DVA-C02 exam, this scenario tests your understanding of application-layer security on an Application Load Balancer, often appearing as a distractor against options like encrypting the cookie payload or using sticky sessions alone—remember that ALB-generated cookies already support encryption, but flags enforce transport and script-level protection. A common trap is confusing cookie attributes with backend session management; the key is that these flags are set on the cookie itself, not on the ALB listener. Memory tip: think “S for Secure, H for HttpOnly” as your “SHield” against hijacking.
DVA-C02 Security Practice Question
This DVA-C02 practice question tests your understanding of security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company hosts a web application on EC2 instances behind an ALB. The application uses cookies to track user sessions. The security team is concerned about session hijacking. Which action should be taken to protect the cookies?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set the Secure and HttpOnly flags on the session cookie.
Setting the Secure and HttpOnly flags on the session cookie is the correct action because the Secure flag ensures the cookie is only sent over HTTPS, preventing interception via man-in-the-middle attacks, while the HttpOnly flag prevents client-side scripts (e.g., JavaScript) from accessing the cookie, mitigating cross-site scripting (XSS)-based session hijacking. This directly addresses the security team's concern by hardening the cookie against common attack vectors without requiring architectural changes.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Enable encryption on the ALB using a custom SSL certificate.
Why it's wrong here
Encryption protects data in transit, not the cookie attributes.
✗
Store session data in ElastiCache instead of cookies.
Why it's wrong here
This reduces cookie size but does not protect against hijacking.
✓
Set the Secure and HttpOnly flags on the session cookie.
Why this is correct
These flags prevent cookie theft via XSS and ensure transmission over HTTPS only.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use AWS WAF to block requests without a valid session cookie.
Why it's wrong here
WAF cannot enforce cookie attributes; it can only block based on rules.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse encryption of the connection (Option A) with securing the cookie itself, or they assume moving session state server-side (Option B) eliminates the need for cookie security flags, when in fact the session identifier cookie still requires Secure and HttpOnly protection.
Detailed technical explanation
How to think about this question
The HttpOnly flag is defined in RFC 6265 and instructs the browser to exclude the cookie from the Document.cookie API, making it inaccessible to JavaScript even if an XSS vulnerability exists. The Secure flag, also per RFC 6265, mandates that the cookie be sent only over HTTPS connections; if the application inadvertently serves a page over HTTP, the cookie will not be transmitted, reducing exposure. In practice, a common oversight is setting these flags only on the login cookie but not on the session cookie, leaving the session token vulnerable to theft via network sniffing or XSS.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Security — This question tests Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Set the Secure and HttpOnly flags on the session cookie. — Setting the Secure and HttpOnly flags on the session cookie is the correct action because the Secure flag ensures the cookie is only sent over HTTPS, preventing interception via man-in-the-middle attacks, while the HttpOnly flag prevents client-side scripts (e.g., JavaScript) from accessing the cookie, mitigating cross-site scripting (XSS)-based session hijacking. This directly addresses the security team's concern by hardening the cookie against common attack vectors without requiring architectural changes.
What should I do if I get this DVA-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DVA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DVA-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.