What's the first thing to do Initiation workshop? (Welcome meeting or kick-off meeting) Define team members Product vision document Prioritization of User Stories.
What is NOT the responsibility of the Tech Lead? Be the user Technical solution Best practices (Lead development team and keep it focused on delivering on time, with quality, while following best practices) Protect dev team from disruptions (alongside PO).
What is NOT part of Project Control in the Solution Release? Go/no Go decision Bug fixing UAT.
What is APDEX? Outsystems uses the APDEX (Application Performance Index) metric, to measure the user satisfaction with the performance of your applications. APDEX shows developers how the application is performing prior to the product roll out.
You're the tech lead and you're in the solution release phase and there are some hotfixes to do... You register the bugs and propose to fix them in the next release in order not to delay the release Fix and pass the release anyway Schedule UAT tests on alternate days and fix the hotfixes in those deliveries.
Which functions are part of the developer? Implement and test user stories Write, implement, and test user stories Only implement.
There is a doubt during the implementation of a user story, but the PO is unavailable. What should you do? Wait for the PO to come back Go ahead with the development assuming your idea Ask the BA to clarify the doubt.
What is Moscow (Must-have, should-have, could-have, and won’t-have) used for? Writing user stories Prioritizing user stories.
What are the goals of the solution delivery? Time to market, Response to change, Value to end user In the initiation phase writing extensive documentation then following that plan in order to deliver the product.
When deploying an application... what permissions should the user have have? Change and deploy on target Change and deploy on source.
What should not be done in the Stabilization process in the Solution Release? Implement User Stories from backlog Hot bug fixing Testing.
Which logs are NOT recorded by the platform by default? SOAP and REST calls. Extensions methods call... General Logs created by action Log All errors.
Assume that you are deploying an application from Dev to QA in lifetime. What can NOT you do? Abort the deployment Create a new deployment plan with the same environments Create a new deployment plan with different environments Consult the deployment plan status with a different user.
What should be done in Post Production phase? Tuning and Hot fixing Testing Stabilization User Guide Document.
First thing to do in the Initiation Workshop Vision Document Define users e personas Define US Mock-ups.
What are the 3 cycles that occur within of an Iteration Development: Initiation, Build and Release Build, Accept and Release Shape, Build and Accept Initiation, Shape and Build.
What Not to do during the Initiation Workshop Write User Stories Define the solution architecture Define team members Design UI Mock-ups.
Regarding roles in Lifetime, regarding the user in an infrastructure, how can you have roles
Per environment, application and teams Per infrastructure, per environment, application and teams Per infrastructure Per environment.
What is the effect of having a cyclic reference between two modules It's the only way to generate indirect references to the consumers of those modules Generates loops in the runtime code Although modules involved in the cycle become tightly connected, it allows a better granularity without extra impacts on other consumers One of the directions is conceptually undesirable, with hard-to-manage code .
transparency service is applicable when: Integrating with an ERP supporting different functional areas Abstracting several concepts in a single API To compose several concepts into a single API To make a core service agnostic to the fact that the same type of Master data is coming from different external system of records.
What is the best way to compose applications in this example? End user App: EU1 + EU2, Core App: Core A + Core B + Core C, Library APP. Library A + Library B + Library C End user App 1: EU1 + Core A + Library A, End user App 2: EU2 + Core B + Core C + Library B + Library C End user App 1: EU1, End user App 2: EU2, Core App: Core A + Core B + Core C, Library APP. Library A + Library B + Library C End user App 1: EU1 + Core A + Library A, End user App 2 : EU2, Core APP Core B+ Core C + Library B + Library C.
Abstraction is key to promote The development of logic and data around business concepts directly in an end-user module, if those concepts are only
used in that module The split of a concept into different modules to separate data, logic and presentation layers The capacity to create/update/delete entity records directly in a end-user module Information hiding to easy the reuse of functional and non functional concepts .
Imagine you need to extract a core from an end user module. Why would you keep consumed elements on the original module (step 5)? Ver 4 !! To change the URLs and force consumers to refresh dependencies To keep all screens and entities on the original eSpace, preventing consumers to refresh dependencies To keep all screens and entities on the original eSpace, avoiding data migration To reduce impacts on consumers and leave the original name to the clone of the end user module to keep URLS.
What is the benefit of a good Architecture? Reduces risk by avoiding Service Abstraction Manages complexity and reduces costs, removing the need to plan Abstracts business concepts, making unnecessary to worry with non functional requirements Makes dependencies manageable and solutions flexible to evolve .
What is important to understand, when disclosing concepts for an architecture design End user processes, business concepts, integration needs and NFRs Detailed user stories and signatures of all the required APIs The availability of different teams involved in systems to integrate The major project risks.
What is the nature of an Orchestration module? Provides non reusable functionality to support user stories Orchestrates the synchronization of multiple entities from an external system of records Provides reusable business processes but must not be consumed by other end-user modules Manages cross-application processes and dashboards, providing access to different business applications.
What is a good reason to split a core module in two To make sure that entities are isolated from business logic To avoid upward references To increase development speed To separate unrelated concepts with different lifecycles.
A Core module should... Provide reusable services around a business concept, as long as it is not consumed by another Core module Be isolated to avoid impacts from changes on external consumers and producers Provide business or non business reusable services, and it can depend on other Core modules Be exposed to external consumers through an Integration Service and reference external producers through an API module .
What is the the goal of a correct application composition? Minimize impacts between modules Allow different paces in modules of the same Application Aggregate modules of same functional area, for different sponsors Simplify deployments.
How can you fix an upward reference from a library Always move the consumed elements from the producer to the consumer to avoid the reference Simply remove the references to the elements of the upper layer module Identify the consumed elements and move them to a reusable core module Make sure the library is business agnostic and move consumed elements to reusable libraries.
What is the consequence of having upward references The footprint of the modules reduce drastically Allows the correct reuse of screen destinations in a menu Reduces the number of indirect references, by shortcutting to an upper layer module Generates a lot of direct or indirect cyclic references.
Why is it so important to have a multi-layer framework to support Architecture Design? To promote a correct abstraction of reusable services. To optimize lifecycle independence. To minimize impact of changes. All the options are correct.
What is the main nature of an end-user module? Provides functionality to support user stories, and must be independent of other end-user modules Provides reusable business processes but must not be consumed by other end-user modules Orchestrates cross-application end-user functionality Designed by an end-user.
Consider the following example of an External Core Service with local replica, where the Master of Customer is an external ERP. Consumers of the Core Service are not able to compose customer information with aggregates The ERP API must support a complex API to cover all use cases of searching and filtering customers Optimizing the synchronization process has no impact on consumers of the core service The ERP is protected from end user load since there is a synchronization process.
Which of the following options describes a valid reason to create a Calculation Engine (_Eng) module? To abstract different complex logic implemented in several Business Logic modules. To support a concept with entities and CRUD edition. To support complex calculations (e.g. an insurance simulator). To support reusable Actions from Core Widget modules.
Check the following blueprint where a shared Style guide provides the menu and the Login flow in the theme. In this situation, what is the applicable scenario? Independent App There is no applicable scenario Intranet Portal.
What is the best approach to fix a cyclic reference between two modules Remove the composition logic to a third module that consumes these two modules Make the module independent, by replicating the common code required in both modules Always merge them in a single module Identify the undesirable direction and replace action references by a REST API reference.
Should you join unrelated concepts in the same module? Yes, because it reduces the number of references, simplifying deployments Yes, to avoid cyclic references and reduce the footprint of generated code No, because it adds unnecessary complexity to consumers requiring both concepts No, because it prevents lifecycle independency of concepts and add unnecessary impacts to consumers.
What is the consequence of having side references Lack of isolation between core modules Always generates cyclic references Allows the reuse of destinations between end user modules No lifecycle independence between end user modules.
Check the following blueprint where a shared Style guide provides the menu in the template and the login flow on the theme. In this situation, what is the applicable scenario? There is no applicable scenario Independent App Intranet Portal.
Why is reusability so important? Promotes cost savings by allowing the definition of a concept in multiple modules Gives flexibility to create/update/delete entity records directly in a end-user module It allows sharing screens between different end user modules Promotes cost savings and avoid multiple definitions of concepts.
When should you mix modules from different owners in the same application? To make sure all modules get the same quality To prevent different lifecycles To simplify deployments Never, each application must have clear accountability set to support deployment decisions.
Select a valid reason to create a BL module To abstract different implementations in a Transparency pattern To support a concept with entities and CRUD edition To support reusable core widgets To implement business rules by composition of base core modules.
What is the first thing to ensure to correctly compose applications? No cycles among applications Application of a certain layer should only contain modules of that layer Applications must be manually positioned in a layer Modules correctly layered with no violations.
In which of the following scenarios should a custom Style Guide be implemented? Whenever applications cannot benefit from any existing theme. The Style Guide should be implemented by cloning the most complex template available, to leverage the Blocks and Actions from the original template and accelerate developments. Whenever applications cannot benefit from any existing theme. The Style Guide should be implemented by starting from the most basic template possible, since it only contains the minimum required structure to start. Whenever an application needs to have independent deployments and low-level of interdependence among other
applications. Always. Every project / application should have their own custom Style Guide.
Adoption of the 3-layer canvas provides An automatic way to follow and fix architecture principles A common understanding between business users A systematic approach to architecture design, supported by a validation tool Faster architecture design without validation need.
What is a good reason for joining concepts when assembling a module? Concepts have the same lifecycle, even if not functionally related To reduce the number of modules and references, simplifying the release cycle To accelerate development, by reducing the number of references Concepts belong to the same functional area and a typical consumer exercise all the concepts “.
Consider the following scenario: You have multiple applications with the same look and feel as an existing built-in style guide. All applications reuse the same federated authentication. The Style guide is an specialization of the built-in and the Login flow is in the template The Style guide is a clone of the built-in and the Menu is in the theme The Style guide is a clone of the built-in and the login flow is in the template The Style guide is an specialization of the built-in and the Login flow is in the theme.
What is the correct way to fix a side reference? Replace destinations by external URLs and consume actions through restfull APIs Make sure the consumer is business agnostic and move consumed elements to reusable libraries Always move the consumed elements from the producer to the consumer to avoid the reference Identify the consumed elements, excluding destinations, and move them to reusable core/library modules.
The correct granularity of modules in the Canvas, promotes: The merge of two concepts on the same module whenever one depends on the other The reusability of end-user modules by spliting business processes per module The mandatory split of one concept into different modules, separating data, logic and presentation The segregation of reusable building blocks that minimizes impacts on consumers.
Consider the following statement: “In OutSystems 11, it is recommended to use business-related Screens in Foundation layer modules, since it does not break any Architecture validation rule.” Which of the following options is correct? The sentence is true for all business-related Screens. All references to Screens are weak, so they can and should be used in Foundation Layer modules, without causing upward references. The sentence is false. Although all references to Screens are weak, only non-business related Screens should be used in Foundation layer modules. The sentence is true for business-related Web Screens. References to Mobile Screens are still considered strong references, so they should not be used in Foundation Layer modules. The sentence is false. Although all references to screens are weak, only business-related Screens that are not being consumed by other modules should be used in Foundation layer modules.
Consider the following Discovery example, showing the consumers of End User application CRM and pick the solution that better improves applications lifetime Isolate modules CRM Biz and Policies Biz in a Core application Isolate all the end user modules in different applications Move the consumed library modules to a library application Move the consumed modules to a core application.
What is the impact of having so many violations in this application canvas? Unbalanced proportion of core applications, but still a reasonable lifecycle independence among end user / Orchestration applications The only way to solve all the upward references is by refactoring the modules inside each application It is impossible to move modules between applications Unmanageable deployments in lifetime.
When integrating with an ERP with hundreds of APIs, across several business areas, you should: Create a single Integration Service to map concepts and hide integration complexity Create a Driver module per functional area and an Integration Service on top to have a single endpoint to communicate with the ERP Use the REST/SOAP API exposed by the ERP directly in your business rules Create an Integration Service, per functional Area, with the correct granularity to fulfill different lifecycles and consumption needs.
During refactor, which prioritization should be checked after End-users modules are ok? Cycles among end users Upward references to cores Cycles among libraries Cycles among cores.
What is the main reason, when refactoring, to freeze features before the refactored code hits production? To make sure that all the focus goes to the refactoring To avoid enlarging the code requiring refactoring This assertion is false. Refactoring while changing/adding features is a way to dilute refactoring cost Because new definitions on elements being refactored, may not match what is in production, when trying to reconnect data.
Consider the following example of a basic External Core Service, where the Master of Customer is an external ERP The integration service only needs to support the retrieval of customer updates since the last sync Consumers of the Core Service will be able to compose customer information with aggregates The ERP is protected from end user load since there is no synchronization process The ERP API must support all customer info retrieval needs, since there is no local replica in the core service.
Adopting a module naming convention is important to Remove the need to validate the architecture Understand the mapping between modules and applications Reveal the nature of each module, without enforcing a reference architecture Enforce a reference architecture and normalize patterns.
Which of the following options describes a benefit of adopting the Architecture Canvas? The Canvas provides a systematic approach to architecture design, supported by a validation tool The Canvas provides an automatic way to follow and fix architecture principles. The Canvas provides a way to easily promote the collaboration and understanding of the business users The Canvas provides faster architecture design without validation needs. .
How to improve an External Core Service with local cache, when the whole database is too big and costly to synchronize and you need to list and search? (Details are only required for single entries) Adopt a lazy load strategy, where the local cache is incrementally updated, whenever single records are requested from the external system Make sure the synchronization logic is separate from the core service to reduce impacts Avoid the local cache to remove the synchronization cost without performance impacts Sync only summary data that it's frequently listed, joined or searched and get full detail directly from the external systems when a single entry is selected.
In which of the following scenarios should you choose to clone a built-in Style Guide? When it is not possible to benefit from any existing theme and extensive changes are needed. When minor customizations to the base theme should be done inside the app theme. When you want to introduce extensive changes to an existing theme. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
Consider the common style guide scenarios presented in this course. Which of the following statements is True? The "specialize a built-in Style Guide" scenario should be used when the changes to the base theme are not extensive. Build-your-own Style Guide should be used when the changes in the theme are not extensive. The "clone a built-in Style Guide" should be used when you want to extend an existing theme.
Elements such as the menu and login can be shared across different apps. In a specific use case, both the menu and login are defined inside the theme. Which use case is this? Portal Independent Apps Intranet.
Which of the following options denotes the advantages of defining a Style Guide up front? Security and scalability. Improve performance and maintainability. Speed up the development phase. Allows apps and the Style Guide to be deployed to Production.
Which of the following options is not an output of Project Initiation? Vision Document. Detail of what will be delivered in each iteration. Definition of Ready and Definition of Done checklists. Delivery Practice Alignment.
One of the most important tasks of the Iteration Development phase is to write and prioritize the backlog for an Iteration X. When should this task be done? In the previous iteration (X-1). At the beginning of iteration X. During iteration X. At the end of iteration X.
During the Iteration Development Phase, when do the Shape, Build and Accept tracks occur in an iteration? Consecutively. The iteration should start with the Accept of the previous iteration, then Build and finally the Shaping of the next iteration is done. Consecutively. The iteration starts with the Shaping of the iteration, then Build, and finally Accept to close the iteration. Shape and Build happen concurrently, taking around 70% of the iteration timeline. After both end, Accept takes the remaining 30% of the iteration. Concurrently. Build takes the whole iteration timeline, Shape starts half way through and Accept happens at the beginning or the end of the iteration. .
Considering the Solution Release phase, which of the following options is true? A rule of thumb for the duration of the Solution Release Phase is: one week of Solution Release, for two weeks of Iteration Development. Training is the responsibility of the Tech Lead, or when unavailable, of the Delivery Specialist. No new developments or any other major tasks should take place in this phase. The rollout plan exclusively focuses on a step by step technical deployment script. .
How many database tables compose the environment log system? Twelve tables Ten tables Nine tables Two tables.
Can you customize the retention period of logs in the outsystems cloud? Yes, the retention period can vary from two to nine weeks No, the retention period is fixed at nine weeks.
Inside the service center in the Monitoring tab how old can be the logs presented? Two weeks or less Three weeks or less Nine weeks or less.
What is the maximum amount of time environment logs are kept for? Nine weeks Five weeks Two weeks In all cases the maximum retention period can be set from two to nine weeks.
|
