While developing a public website using AEMaaCS, a client introduces a new requirement on the ability for users to leave comments on the site's pages. How would the Solution Architect respond to ensure the design remains flexible and prepared for potential future modifications while adhering to GDPR regulations?
Suggested Answer: A
Get Premium AD0-E117 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
18 comments · newest first
JA
Jamey
2 days ago
C sounds good. NoSQL is flexible for growth.
LA
Layla
7 days ago
I prefer B. Built-in features are reliable.
KY
Kyoko
12 days ago
I think A is the best choice. Keeps things separate.
ST
Stefany
17 days ago
B is efficient. Synchronization is key for performance.
JU
Judy
22 days ago
A ensures GDPR compliance. External vendor is reliable.
EV
Eva
28 days ago
D sounds risky. Pull mechanisms can lag.
TA
Tamekia
1 month ago
C could be flexible, but NoSQL might complicate things.
IS
Isaiah
1 month ago
B seems easier for integration. Built-in features are handy.
CH
Chau
1 month ago
I think A is a safe choice. Keeps data separate.
JA
Jarod
2 months ago
Wait, can we really trust an external vendor with user data?
VE
Verona
2 months ago
D) sounds risky, what if the main instance goes down?
BE
Bette
2 months ago
C) NoSQL could work, but is it really necessary?
LE
Lettie
2 months ago
B) is more efficient for scaling, though.
SH
Shawn
2 months ago
A) seems like the safest bet for GDPR compliance.
HA
Hailey
2 months ago
I’m a bit confused about the pull mechanism in option D; does it really ensure compliance with GDPR? I need to think more about that.
JO
Joanne
3 months ago
I feel like we practiced a similar question about data storage options, and I leaned towards NoSQL for flexibility, so option C could work too.
EL
Elfrieda
3 months ago
I’m not entirely sure, but I think option B might be better for performance since it uses the native repository.
OS
Osvaldo
3 months ago
I remember we discussed the importance of keeping user data compliant with GDPR, so option A seems like a safe bet.