Question-1: Load testing tools are pieces of software that recreate real world load conditions so that applications or websites may be subjected to such conditions in a secure and managed setting. Load testing tools will monitor and report on the performance of the application or website while it is being subjected to various simulated usage settings in order to find lags or problems. You are assisting the quality assurance team in the rollout of a new load-testing tool in order to verify the scalability of your key cloud services that are powered by Google Compute Engine and Cloud Bigtable. Which three requirements need to be included in the package? (Choose three.)
A. Check to see that the load tests demonstrate that Cloud Bigtable is functioning properly.
B. Create a second project on Google Cloud to use as a load testing environment.
C. Ensure that the load-testing tool is executed at a predetermined time every day in the production environment.
D. Check to see that any third-party systems that your services depend on are capable of managing a high volume of users.
E. In order for the load-testing tool to be able to play back recorded transactions, the production services must be configured to record each transaction.
F. The load-testing tool and the services that you wish to test should both have thorough logging and statistic gathering capabilities.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 1,2,6 Explanation: Option 1: Run your normal workloads against Bigtable: When undertaking capacity planning, you should always run your own typical workloads against a Bigtable cluster. This will allow you to determine how to allocate resources to your applications in the most effective manner. Option-2. Option 6: The most essential and standard element of testing, you collect logs and data in the TEST environment for future scalability. This option requires that you create a new Google Cloud project to utilise as the load-testing environment. It is essential to ensure that the existing Big Table cluster is capable of managing incoming traffic. A cluster needs a sufficient number of nodes to accommodate the workload it is currently experiencing as well as the quantity of data it contains. In the event that this does not occur, the cluster runs the risk of being unable to process newly arriving requests, which results in an increase in latency. Even though it is a managed service, the size of the system cannot be adjusted automatically. It is strongly suggested that a separate project be undertaken. It ensures that it will not share the resources that are associated with your product environment, such as the service quota, and provides you with complete isolation from that environment. In order to use the Load-Testing tool, you will need to create a separate project. At the very least, this would partition the role-based access for development and testing. In addition, each test will have its own code, project, and configuration in order to exclude the possibility of a collision.