Exam Code : Magento-Certified-Professional-Cloud-Developer
Exam Name : Magento Certified Professional Cloud Developer
Vendor Name :
"Magento"
Magento-Certified-Professional-Cloud-Developer Dumps Magento-Certified-Professional-Cloud-Developer Braindumps Magento-Certified-Professional-Cloud-Developer Real Questions Magento-Certified-Professional-Cloud-Developer Practice Test Magento-Certified-Professional-Cloud-Developer dumps free
Magento Certified Professional Cloud Developer
https://killexams.com/pass4sure/exam-detail/Magento-Certified-Professional-Cloud-Developer
After installing a Magento extension that implements a new class for a site and deploying this to an integration environment, you see it is not working. In the logs, you discover the following error:
The specified /app/generated/code/MyCompany/MyModule/MyClassFactory.php could not be written failed to open stream: Read-only file system
How do you fix this?
A support ticket should be filed with Magento Commerce Cloud to fix the filesystem issue.
The extension should be modified so it does not write to generated at runtime.
The file should be generated locally and pushed via Git.
The GENERATED_CODE_WRITABLE variable should be set to true whenever using extensions.
Reference: https://support.magento.com/hc/en-us/articles/115002541893-Error-read-only-file-system-when-accessing-the-read-only-directory-var-generation-
Your project is in a phase where the locales that will be used are still being determined. You need to configure your project in a manner that will allow them to be changed dynamically. How can you accomplish this?
Remove the system/default/general/locale configuration from the app/etc/config.php file
Configure SCD_ON_DEMAND to true in the .magento.env.yaml file
Run the command vendor/bin/ece-tools locales:unlock on the environment
Configure DYNAMIC_LOCALES in the SCD_MATRIX to true in the .magento.env.yaml file
Reference: https://devdocs.magento.com/cloud/live/sens-data-over.html
The merchant wants to offer specific pricing in different currency markets, so you have set up multiple websites to cover each currency. Now they want customers to be directed to the appropriate website based on the country they are in.
How do you configure this?
Use the Country Mapping in the Fastly settings to map country codes to store views.
In the Project Web UI, enable the Website IP Mapping setting.
Update magento-vars.php to detect the country code from the IP address and map it.
Build or install a Magento extension that changes the default currency code on application init.
What do you do to reduce site downtime?
Set the SKIP_MAINTENANCE_SCD variable to true in the .magento.env.yaml file.
Add a custom command to the post_deploy phase to activate deferred deployment.
Move custom commands from the deploy phase to the build phase.
Update the SCD_MATRIX variable to include only necessary custom commands.
You want to improve the ability to monitor Production deployments by setting up an email notification system. How do you achieve this?
Enable Deployment Notifications under Configure Environment > Settings in the Project Web UI
Build a custom module which hooks into the deployment phase and sends emails in real-time
Configure log notifications in the .magento.env.yaml file
Use the magento-cloud environment:deploy:email command to enable email notifications
Reference: https://devdocs.magento.com/cloud/env/setup-notifications.html
A merchant with three websites using en_GB, fr_FR and de_AT requires a change in locale to de_DE for the German Production website. After running the following command on Production you notice the frontend design of the German website is broken:
php bin/magento config:set --scope=websites --scope-code=german general/locale/code de_DE
Static content deployment is set up on the deploy phase. Why did this happen?
Static Content is not pre-generated for the de_DE locale
de_DE is not writeable in pub/static and has to be configured via the .magento.app.yaml file
The magento-cloud environment:deploy command has not been run yet to generate static content for the new locale
STATIC_CONTENT_SYMLINK is not configured in the .magento.env.yaml file
QUESTION 59 To secure composer credentials you want to remove the auth.json file from the project repository.
How do you do that?
The build phase runs on a separate server and variables are not available there, you must keep the credentials in the auth.json file, but you can replace the password with its hash
Add the env:COMPOSER_AUTH variable on the project level and make it visible on the build phase
Put the composer credentials into /mnt/build/.config/composer/auth.json
Add the COMPOSER_AUTH variable with the sensitive option enabled
What is prohibiting the email from sending?
You have not enabled the Magento Email module with bin/magento module:enable
The Outgoing Emails setting is disabled under Environment Settings in the Project Web UI
Email is always disabled on all integration branches
You have not configured SendGrid for this environment