Q: 4
You have developed a CAP project and added the XSUAA security configuration. What information is
stored in the xs-security.json file? Note: There are 2 correct answers to this question.
Options
Discussion
A and D imo. xs-security.json is all about defining role-templates (A) and scopes (D) for your app, not actual users or static "roles" like C. Every CAP project I've touched with XSUAA matched this structure. I think that's right but open to other takes if SAP changed things.
Honestly, SAP always confuses with this stuff. Its D and C.
Pretty sure it's A and D since xs-security.json is used to define role-templates and scopes for XSUAA. Not seeing direct user or concrete role assignments there. Unless SAP changed something recently, these are the usual config keys.
Its A and D. xs-security.json is where you define role-templates and scopes, not actual users or concrete roles. Saw a similar question in some practice sets. Pretty sure about this but feel free to correct me if SAP updated something.
A and D for sure. xs-security.json is where you define scopes and role-templates, not actual users or roles themselves. Been the same in all my CAP projects unless SAP suddenly changed syntax. Anyone seen different structure lately?
A and D imo. xs-security.json defines role-templates and scopes, not users or direct roles. Seen this structure a lot in CAP+XSUAA setups, but not 100 percent if SAP changed naming conventions lately. Agree?
I don’t think it’s C. A and D look right since xs-security.json sets up role-templates and scopes, not actual roles. People often mix up roles with templates in SAP docs.
I don’t think it’s B or C. A and D make sense here since xs-security.json configures role-templates and scopes for XSUAA to enforce auth rules, but not users or real role entities. Seen similar structure in actual CAP tutorials. Let me know if I missed something.
Probably A and D for this one. The
xs-security.json mainly defines role-templates and scopes, not actual users or direct role assignments. Pretty sure that's what SAP expects here. Agree?Be respectful. No spam.
