C_SEC_2405 · Question #26
Which authorization objects can be used to restrict access to SAP Enterprise Search models in the SAP Fiori launchpad? Note: There are 2 correct answers to this question.
The correct answer is B. SDDLVIEW D. S_ESH_CONN. Restricting access to SAP Enterprise Search (ESH) models in the Fiori launchpad requires authorization at two levels: SDDLVIEW (B) controls access to the underlying CDS (Core Data Services) views that ESH models are built upon, while S_ESH_CONN (D) governs access to ESH…
Question
Which authorization objects can be used to restrict access to SAP Enterprise Search models in the SAP Fiori launchpad? Note: There are 2 correct answers to this question.
Options
- AS_ESH_ADM
- BSDDLVIEW
- CRSDDLTIP
- DS_ESH_CONN
How the community answered
(18 responses)- A17% (3)
- B78% (14)
- C6% (1)
Explanation
Restricting access to SAP Enterprise Search (ESH) models in the Fiori launchpad requires authorization at two levels: SDDLVIEW (B) controls access to the underlying CDS (Core Data Services) views that ESH models are built upon, while S_ESH_CONN (D) governs access to ESH connectors, which are the bridge between the Fiori launchpad and the search models themselves - together, these two objects form the complete access control chain for ESH models.
S_ESH_ADM (A) is a distractor because it's an administration authorization object used for managing the Enterprise Search infrastructure (index configurations, system settings), not for restricting end-user access to specific models. RSDDLTIP (C) is unrelated to Enterprise Search model access - it belongs to a different functional area and is not a valid control point for ESH in Fiori.
Memory tip: Think "CD" - CDS views (SDDLVIEW) + Data connector (S_ESH_CONN) = the two layers you must lock down. If you see "ADM" in an option, mentally flag it as admin-only, not user-access control.
Topics
Community Discussion
No community discussion yet for this question.