Certificate Associate Exam - Back-end Developer PT12

<CDS Basics: DDL vs DCL> What file type do you use to define the structure and logic of a CDS view?. .ddl. .dcl. .cds. .ddic.

<CDS Basics: DDL vs DCL> Which annotation is required in a CDS view to activate DCL-based access control?. @AccessControl.authorizationCheck: #NOT_REQUIRED. @EndUserText.label: 'Sales Order View'. @AccessControl.authorizationCheck: #CHECK. No annotation is needed; DCL will work automatically.

<Session Variables in DCL> In a DCL file, how do you reference the current user to filter data?. Customer = $session.user. Customer = SESSION_USER. SalesOrder = $session.user. Customer = system_user.

<Annotation Without DCL> You define @AccessControl.authorizationCheck: #CHECK in a CDS view but do not create a DCL file. What happens at runtime?. The user sees all data — DCL is optional. The user gets a short dump. The view shows no data at all — access is completely denied. An error message is displayed saying “No DCL found”.

<DCL Without Annotation> You create a DCL file, but your CDS view has @AccessControl.authorizationCheck: #NOT_REQUIRED. What happens?. The DCL rules are applied correctly. Only administrators can access the data. All users see all data — the DCL is completely ignored. The system throws an error for conflicting settings.

<DCL Syntax & Logic> Which of the following is the correct syntax for defining a DCL file for a CDS view?. define access for Z_CDS_SalesOrder { grant select on view where ( Customer = $session.user ); }. define role ZROLE_SALESORDER { grant select on Z_CDS_SalesOrder where ( Customer = $session.user ); }. define access control Z_CDS_SalesOrder { filter rows by Customer using $session.user; }. define control for Z_CDS_SalesOrder { restrict where Customer = $session.user; }.

<DCL Syntax & Logic> How do you combine two conditions (Customer = user, and SalesOrderType = 'OR') in a DCL?. where ( Customer = $session.user ) and ( SalesOrderType = 'OR' ). filter by Customer and SalesOrderType. where ( Customer = $session.user and SalesOrderType = 'OR' ). restrict rows where Customer = $session.user and SalesOrderType = 'OR'.

<RAP & DCL Integration> In a RAP-based Fiori app, what happens when a DCL role restricts the CDS view behind the app?. The user sees only rows allowed by the DCL — RAP behavior has no impact on read access. The user sees all rows, and RAP behavior restricts the display after loading. The DCL is ignored because RAP apps use their own access control. The user gets a warning message saying "Access restricted by DCL".

<Fail Behavior> What happens if access is denied by DCL in a Fiori app?. The user is redirected to login again. No rows are shown — it fails silently. The system dumps. The screen shows "Access Denied".

<DCL vs RAP Behavior Responsibilities> What is the primary difference between DCL and RAP behavior classes?. DCL is used only in test environments. DCL applies row-level visibility; behavior classes define business logic and actions. DCL is optional in RAP; behavior classes replace it entirely. DCL manages data validation; behavior classes restrict data access.