Which two project situations favor a waterfall methodology? Choose 2 answers
A. An application with many systems and inter-dependencies between components.
B. An application with regulatory compliance requirements to be validated by outside agencies.
C. An application in post-production, with incremental changes made by a small team.
D. An in-house application with a fixed team size, but an open timeline and flexible requirements.
Explanation:
An application with many systems and inter-dependencies between components is a project situation that favors a waterfall methodology, as it requires a high level of planning and design upfront to ensure the integration and compatibility of the components. An application with regulatory compliance requirements to be validated by outside agencies is also a project situation that favors a waterfall methodology, as it requires a clear and detailed documentation of the requirements and specifications, as well as a formal and rigorous testing and validation process. An application in post-production, with incremental changes made by a small team is a project situation that favors an agile methodology, as it allows for faster and more frequent delivery of changes, as well as more flexibility and collaboration. An in-house application with a fixed team size, but an open timeline and flexible requirements is also a project situation that favors an agile methodology, as it allows for more creativity and experimentation, as well as more feedback and adaptation.
What are three advantages of using the SFDX? Choose 3 answers
A. Can store code on a local machine, or a version control system.
B. Can quickly deploy metadata using Execute Anonymous.
C. Can create scratch orgs.
D. Can use native Deployment Rollback Tool to quickly revert to prior state.
E. Can Install application metadata from a central repository.
Explanation:
Three advantages of using the SFDX are: can store code on a local machine, or a version control system; can create scratch orgs; and can install application metadata from a central repository. These advantages can help improve the development experience, as they allow developers to work with source-driven development, use ephemeral and configurable environments, and access metadata components from a shared location. Can quickly deploy metadata using Execute Anonymous is not an advantage of using the SFDX, as Execute Anonymous is a feature of the Developer Console that allows running Apex code, not deploying metadata. Can use native Deployment Rollback Tool to quickly revert to prior state is also not an advantage of using the SFDX, as there is no such tool in the SFDX. See [Salesforce DX] for more details.
Sales and Service products will be created by two teams that will use second-generation managed package(s). The Sales team will use a specific function of the Service product, but the architect wants to ensure that this team will only use the functions exposed by the Service team. No other team will use these same functions. What should an architect recommend?
A. Create two second generation managed packages with the same namespace and set the methods that should be shared with the @namespaceAccessible annotation.
B. Create two managed packages with Sales and service namespaces. Set the methods to be shared with the ©salesAccessible annotation
C. Create a managed package with both products and create a code review process with an approver from each team.
D. Create two managed packages. Create an authentication function in the Service package that will return a token if a Sales user is authorized to call the exposed function. Validate the token in the Service functions.
Explanation:
The architect should recommend creating two second generation managed packages with the same namespace and setting the methods that should be shared with the @namespaceAccessible annotation. This will allow the Sales team to access the specific functions of the Service product without exposing them to other teams or customers. Creating two managed packages with different namespaces will not allow the Sales team to access the Service functions, unless they are declared as global, which will expose them to everyone. Creating a managed package with both products will not allow the separation of the products and the control of the functions. Creating an authentication function in the Service package will add unnecessary complexity and overhead to the solution.
Metadata API supports deploy () and retrieve () calls for file-based deployment. Which two scenarios are the primary use cases for writing code to call retrieve () and deploy () methods directly? Choose 2 answers
A. Team development of an application in a Developer Edition organization. After completing development and testing, the application is Distributed via Lightning Platform AppExchange.
B. Development of a custom application in a scratch org. After completing development and testing, the application is then deployed into an upper sandbox using Salesforce CLI(SFDX)
C. Development of a customization in a sandbox organization. The deployment team then utilize the Ant Migration Tool to deploy the customization to an upper sandbox for testing.
D. Development of a custom application in a sandbox organization. After completing development and testing, the application is then deployed into a production organization using Metadata API.
Explanation:
The Metadata API is mainly used for file-based deployment, such as deploying an application from a Developer Edition org to the AppExchange, or from a sandbox org to a production org. The Ant Migration Tool is a wrapper around the Metadata API, so it is not a direct use case for writing code to call retrieve() and deploy() methods. The Salesforce CLI (SFDX) uses the Source-Driven Development model, which relies on the source code as the source of truth, rather than the Metadata API.
Ursa Major Solar (UMS) has used Aura components significantly in its Salesforce application development. UMS has established a robust test framework and the development team follows the Salesforce recommended testing practices. UMS team uses Salesforce’s test tool To check for common accessibility issues. In which two environments the UMS team can call Aura accessibility tests? Choose 2 answers
A. JSTEST
B. ACCTEST
C. WebDriver Test
D. AuraDriver Test
Explanation:
Aura accessibility tests can be called in JSTEST and WebDriver Test environments. JSTEST is a JavaScript testing framework that runs on Node.js and can be used to test Aura components. WebDriver Test is a Selenium-based testing framework that can be used to test the user interface and accessibility of Aura components. ACCTEST and AuraDriver Test are not valid environments for calling Aura accessibility tests.
Page 15 out of 46 Pages |
Previous |