Avaloq ACCP (Complete Questions 2020)
From the avaloq course ACCP. Questions to all Chapters of all 3 Books
From the avaloq course ACCP. Questions to all Chapters of all 3 Books
Fichier Détails
| Cartes-fiches | 248 |
|---|---|
| Utilisateurs | 47 |
| Langue | English |
| Catégorie | Informatique |
| Niveau | Autres |
| Crée / Actualisé | 26.11.2020 / 02.06.2025 |
| Lien de web |
https://card2brain.ch/box/20201126_avaloq_qa
|
| Intégrer |
<iframe src="https://card2brain.ch/box/20201126_avaloq_qa/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
The ACP is build on 3 layers: ...
- data-layer (persisted stored data -> EWOM)
- application-layer (functions, request handling, workflow execution... -> PL/SQL)
- presentation layer (user interface/GUI, display reports ... -> PL/SQL)
The Avaloq Frontplattform consists of ...
- Web Banking
- Frontworkplace (FWP)
While the Frontworkplace (FWP) is for employees in the Frontoffice, the Web Banking is for Clients.
True
The three User Interfaces for the ABS are ...
- SmartClient (Front-, Middle-, Backoffice)
- Frontworkplace (Frontoffice)
- Web Banking (external users)
The SmartClient is organzed into desks. The Areas of the SmartClient are ...
- Avaloq Button (check/change system&session info)
- Ribbon (defines business themes)
- Sidebar (personalized access -> Favorites etc.)
- Work Area
Besides the E-Banking contract Authorities (Access Rights) are needed for an external client to use Web Banking.
True -> while the minimum requirement to log into the E-Banking environment is the contract, to access its functionality and data you need Authorities!
The Access Rights/Authorities in the FWOM are linked to a DOCM (contract) only.
False -> they are linked to atleast a DOCM, a PERSON and a BP
The Authorities/Access Rights in a Web Banking environment (FWOM) are Closed Security.
True
The Avaloq Ice Workbench connects to two things: ...
- source repository (dev1 -> default database)
- Development instance (SAXX user)
If a source type doesn't have a compiler it can only be installed.
True
A source can have exactly one status at a time and several attributes.
False -> only ONE or NONE attribute per source possible (corrupt, error, warning)
API's enable external tools to interact with the ACP instance
True
API's do not speed up the development process, but the application.
False -> API's do not speed up the application, but do speed up the development process
Not supported source types are stored in BTC sources or Component Config sources (this source type is installed first before all others).
True
DDIC's for Reports use the dtm_ || dtm_doc -Format
DDIC's for Code Tables / Extensions use the code_ || code_obj_extn / code_doc_extn -Format.
True
The ADAI (Avaloq Database Automation & Integration) has what purpose?
enables the clients to manage their ACP development infrastructure through continous integration, quality assurance & automation tasks
The ASMD is used for sources in a Context as a Coding support.
True
PL/SQL accesses data via SQL queries, while Avaloq Script access data via DDIC's
True
What is the difference between a procedure and a function?
A procedure re-calculates / creates something with methods/constructors, while a function returns a value (which can be used in a procedure)
The MDB is the new baseline for implementation projects, while the ABR/S is the old baseline.
False -> ABR/S is the new baseline and MDB the old
What is the Naming Convention for CDOE TAB and CODE TAB DEF sources?
ACD$CODE_INSERTNAME
CODE TAB source defines actual values stored in the table, while CODE TAB DEF defines metadata like columns, type of data (number, text ...) and which columns are mandatory or optional.
True
What means the term "any_status" and "any_row" in CODE TAB DEF sources?
any_status = ability to set rows to active/inactive (in CODE TAB)
any_row = ability to override values of any row (in CODE TAB)
Whenever you compile a CODE TAB DEF and CODE TAB source DDIC entries are generated (first time) or updated (all other times)
True
If a Kernel CODE TAB DEF source has no public range, it means the existing rows cannot be modified.
False -> it means a customization specialist cannot add rows to the CODE TAB table
What is partitioning?
Instead of creating huge code tables (CODE TAB), we split them into smaller ones grouped by object type or businesstype
eg.: ACD$CODE_INSERTNAME.BP, ACD$CODE_INSERTNAME.CONT etc.
Order Keys and Object Keys are stored in the sourcetype KEY DEF.
False -> only Object Keys, not Order Keys
Derived Classifications are ...
classifications, which are automatically calculated/set through certain factors (eg. when domicile of a BP is Switzerland, the classification for Branch-Office is set to Zurich)
The Naming Convention for KEY DEF sources is: ...
ACD$"intl_id of code_obj_type"_INSERTNAME (eg. ACD$ADDR_INSERTNAME)
In which DDIC are dynamic values stored?
In the BTT-DDIC
The Cost Rule Engine has different parameters like: OFFSET, ROUNDING_1, ROUNDING_2, MIN_MAX(), FACTOR.
Sort them by their sequence!
ROUNDING_1 -> FACTOR -> MIN_MAX(), OFFSET, ROUNDING_2
If the parameter OFFSET in the Cost Rule Engine is set to eg. "- 40" the cost are lowered by the given amount.
False -> "-" means costs that are charged! So the amount gets added to the Costs
The Condition between different clauses in a Rule Loader Table is AND.
True -> in other words, a rule is only executed if all matching critera are satisfied (not only one)
Multiple matching criteria can be set for a rule clause and these can have either AND or OR conditions.
True
You use the TASK TEMPL source for what?
The TASK TEMPL source stores the combination of a Task, Layout and the Filter Criteria.
Example: Task = bp_list, Filter Criteria = bp_name = "Roland", Layout = "SCREEN REP"
The task input parameters are passed to the TASK DEF source, which triggers a procedure to filter the data according to the parameters. Then it creates a flat datamart. This flat datamart can either be shown directly in a Report Screen, or can be processed in a REP DTM source, where it is converted into a hierarchical datamart.
Finally we can use a REP SCREEN source to define the Layout. Output = Screen Report of a BP-List containing entries, where the BP-Name is "Roland".
A TASK DEF source represents the interface between the Kernel and Report definition layer. A TASK DEF source describes basic task information and all available task parameters in it.
True
A Task is a PL/SQL procedure made available in the User Interface (Smart Client)
True
A (flat) datamart created by a task provided by Avaloq is always customizable.
False -> NEVER customizable
The name of a hierarchical datamart in the REP DTM source starts with "dtm_"
True
In the REP SCREEN source you should use "assign" and not "inherit" for variables.
True
