Magento Magento-Certified-Professional-Cloud-Developer Prüfungsthemen:
| Abschnitt | Ziele |
|---|---|
| Leistung, Sicherheit und Fehlerbehebung | - Empfohlene Sicherheitsverfahren in Cloud-Umgebungen - Strategien zur Leistungsoptimierung (Zwischenspeicherung, Indizierung) - Protokollanalyse und Werkzeuge zur Fehlersuche |
| Architektur von Adobe Commerce Cloud | - Überblick über die Cloud-Infrastruktur (AWS-basierte Architektur) - Projektstruktur und Konfigurationsverwaltung - Umgebungen von Adobe Commerce Cloud (Integration, Staging, Produktion) |
| Bereitstellung und Konfigurationsverwaltung | - Verwendung der Magento Cloud CLI - Umgebungsvariablen und Konfigurationsüberschreibungen - Verständnis des Bereitstellungsablaufs und der Pipeline |
| Anpassung und Entwicklung in der Cloud | - Arbeiten mit den Adobe Commerce APIs - Modulentwicklung und bewährte Verfahren bei Anpassungen - Anpassung von Designs und Änderungen an der Benutzeroberfläche |
Magento Certified Professional Cloud Developer Magento-Certified-Professional-Cloud-Developer Prüfungsfragen mit Lösungen
You upgraded an integration branch in your Magento Commerce Cloud project, but received an error during the deploy phase What are the two ways to review details about the deployment?
Choose 2 answers
- A. View the exception.log file in the var/log/ directory
- B. View the logs in the var/reports/ directory on the remote server
- C. View the cloud.log file in the var/log/ directory
- D. View the depioy.log file in the /var/log/ directory
Antwort: C,D 🗳️
You added the env:ADMIN_PASSWORD variable in the Project Web Ul to change a Magento admin user's password After deployment you are unable to login using the new password What causes this?
- A. Deploy scripts read configuration from the environment variable calledmagento_cloud_variables. which contains an array of variables which were set without the env: prefix
- B. Variables which are set using the Project Web Ul are not available on the build phase the admin password variable should be set in the . magento.env. yaml file
- C. The sensitive option is required for env:ADMIN PASSWORDvariable
- D. When you add a variable. the build stage is being skipped because the codebase has not been changed You must push a commit to trigger a full deploy
Antwort: C 🗳️
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?
- A. Remove the system/default/general/locale configuration from the app/etc/config.php file
- B. Run the command vendor/bin/ece-tools locales:unlock on the environment
- C. Configure DYNAMIC_LOCALES in the SCD_MATRIX to true in the . magento. env. yarn! file
- D. Configure SCD_ON_DEMAND to true in the .magento.env.yaml file
Antwort: D 🗳️
You are reviewing a third party extension for MagentoCommerce Cloudcompatibility Which pattern makes a module incompatible with Magento Commerce Cloud?
- A. Direct instantiation by the objectManager of non-generated classes in .phtml template files
- B. Configuration referencing generated Proxy classes In the modules erc/frontend/di.xml file
- C. Direct instantiation by the objectManager In non-constructor methods with the class also being referenced in the constructor signature
- D. Direct instantiation of generated classes by the objectManager without the class being referenced in the constructor
Antwort: D 🗳️
In a Pro plan project, you notice there is a mail delivery problem in the Integration environment How do you troubleshoot this?
- A. Change the log level in the lcg:emall section of the .magento.env.yaml file
- B. Move the test to the Staging environment
- C. Look In the var/log directory for the mail. log file
- D. Update the SPF record in the DNS
Antwort: B 🗳️
Seite 1 von 12 wird angezeigt.
Fragen 1-5 von 60 werden angezeigt.
993 Kundenbewertungen
