Absolute Free CTAL-TTA_2019 Exam Practice for Comprehensive Preparation 

Subject to testing is a software system (COTS) for Project Administration and Control (PACS). PACS is a multi-project system for controlling the project time, e.g., in terms of scheduling and tracking, and managing the productivity of projects, e.g., in terms of effort and deliverables. During various interviews with stakeholders the following information was gathered: • Using PACS is not business critical. There is no impact such as high financial losses or problems to the operational continuity of an organization. Its application is not critical since the software package does not support directly the operational, or the primary, business processes of an organization. It supports (project) management in the project planning and tracking process. Of course, it will be highly annoying for users if the system “goes down” from time to time. Although this does not have a high impact for the business process as a whole, the Mean Time Between Failures (MTBF) still needs to be at a good level to be successful in the market. • Users of PACS typically have an academic educational level, but have no prior experience with this particular type of project management software. The system will be used by a large number of users within an organization. • The system will be used on a regular basis, e.g., several times per day by project managers and several times per week by project employees. This means that the system will not be used very intensively, often only for some data input or an information request. Its usage is not considered to be very time-critical. • The data is recorded on-line and real-time. The system is expected to run in multiple hardware environments in various network environments. It is also expected that changes in the operational environments will happen in the upcoming period that also need to be supported. Based on the information provided by the stakeholder, which combination of non-functional quality characteristics should you propose to test as part of your test approach?

There are multiple activities the Technical Test Analyst performs regarding test automation. Which of the following activities is a typical test automation activity that the Technical Test Analyst will perform?

Which of the following statements is TRUE regarding tools that support component testing and the build process?

The following user story has been written for a new application being developed to pre-book a space at a National Car Park. As a vehicle driver i want to be able to pre-book a car parking space online, selecting a disabled driver's space if needed So that l can pay in advance and receive confirmation of my parking space number. The following acceptance criteria have also been written: •Payment can be made via PayPal, Debit or Credit Card •Confirmation of payment and car parking details should be sent after the booking process is completed •Driver information is stored in the reservation database The database has been built and tested in a previous sprint, but the interface to the different payment methods have yet to be developed As a tester in an agile team, you have been asked to review the user story You have detected some issues with this story: 1.it needs to cater for different user groups: a driver or disabled driver 2.it needs to cater for different vehicle types: a car. 4x4. van or motorbike 3.There are no acceptance criteria relating to how quick the booking process should be 4.How confirmation is to be sent for payment and space number, and other important details, have not been specified 5.A stub will be needed to test the payment method Which pair of requirements engineering techniques are you MOST LIKELY to have used to uncover these issues’ SELECT ONE OPTION