MicrosoftMicrosoftКаталог

Курс Microsoft AZ-301 Azure Architect Design

Курс Microsoft AZ-301 Azure Architect Design

IT-Training Ви гарантира 100% за качеството на този курс. Ако по някаква причина обучението не отговори на очакванията ви, ние ви гарантираме възстановяване на сумата, която сте заплатили.

Официален Microsoft курс (Microsoft Official Course – MOC) – Курсът е съгласно програмата на Microsoft и основната му цел е подготовка за сертифициране за Microsoft Azure Architect, както и за повишаване на професионалните умения и квалификация.

Формат на курса: Онлайн или Присъствен Курс, Microsoft Official Course, провежда се в реално време от сертифициран инструктор във виртуална класна стая.

Език на курса: български (английски е наличен като опция).

Метериали: в електронен формат, включени в цената.

Пакет от услуги включени към курса:

  • онлайн/присъствено обучение
  • сертификат за завършен курс
  • достъп до виртуален лаб
  • книги и учебни материали
  • достъп до примерни (demo) тестове
  • видео библиотека към курса – достъп до видео записи на сесиите към курса

Курсът е подходящ за: начинаещи в Azure или системната администрация; желаещи да се сертифицират за Azure System Administrator; желаещи да научат Microsoft Azure и да повишат професионалната си квалификация.

Интерактивен формат: участниците имат възможност да участват в дискусии, да задават въпроси, двупосочна връзка с интруктора в реално време, чрез виртуалната класна стая. Онлайн формата се провежда в реално време по график, участниците са свързани наживо, за разлика от видео курсовете при онлайн формата не се презентира видео запис.

График: изберете удобен за вас график от падащото меню.  Курса се провежда в удобно и съобразено с участниците време.

Лабораторна среда: всеки курсист разполага със собствена лаб среда, където се провеждат упражненията, част от курса.

Примерни тестове: позволяват да проверите подготовката си за  сертификационен изпит с примерни въпроси.

Продължителност на курса: 40 уч.ч. онлайн обучение (теория и практика).

Видео библиотека: Можете да преглеждате отново  и по всяко време записите на всички сесии към курса.

Сертификат: всички участници получават сертификат за завършен курс.

Метод на плащане: PayPal, банков превод, наложен платеж, брой, карта.

Ако желаете издаване на фактура, оставете коментар към заявката с необходимата информация.

Дати на провеждане: съгласно календар обучения и обявени събития на нашата Facebook страница.

След създаване на заявка за участие ще се свържем с Вас за потвърждаване на датите.

Ако имате въпроси можете да се свържете с нас, чрез меню контакти.

AZ-301T01: Designing for Identity and Security

AZ-301T02: Designing a Data Platform Solution

AZ-301T03: Design for Deployment, Migration, and Integration

AZ-301T04: Designing an Infrastructure Strategy

Determine Workload Requirements

Gather Information and Requirements

May include but not limited to: Identify compliance requirements, identity and access management infrastructure, and service-oriented architectures (e.g., integration patterns, service design, service discoverability); identify accessibility (e.g. Web Content Accessibility Guidelines), availability (e.g. Service Level Agreement), capacity planning and scalability, deploy-ability (e.g., repositories, failback, slot-based deployment), configurability, governance, maintainability (e.g. logging, debugging, troubleshooting, recovery, training), security (e.g. authentication, authorization, attacks), and sizing (e.g. support costs, optimization) requirements; recommend changes during project execution (ongoing); evaluate products and services to align with solution; create testing scenarios

Optimize Consumption Strategy

May include but not limited to: Optimize app service, compute, identity, network, and storage costs

Design an Auditing and Monitoring Strategy

May include but not limited to: Define logical groupings (tags) for resources to be monitored; determine levels and storage locations for logs; plan for integration with monitoring tools; recommend appropriate monitoring tool(s) for a solution; specify mechanism for event routing and escalation; design auditing for compliance requirements; design auditing policies and traceability requirements

Design for Identity and Security

Design Identity Management

May include but not limited to: Choose an identity management approach; design an identity delegation strategy, identity repository (including directory, application, systems, etc.); design self-service identity management and user and persona provisioning; define personas and roles; recommend appropriate access control strategy (e.g., attribute-based, discretionary access, history-based, identity-based, mandatory, organization-based, role-based, rule-based, responsibility-based)

Design Authentication

May include but not limited to: Choose an authentication approach; design a single-sign on approach; design for IPSec, logon, multi-factor, network access, and remote authentication

Design Authorization

May include but not limited to: Choose an authorization approach; define access permissions and privileges; design secure delegated access (e.g., oAuth, OpenID, etc.); recommend when and how to use API Keys.

Design for Risk Prevention for Identity

May include but not limited to: Design a risk assessment strategy (e.g., access reviews, RBAC policies, physical access); evaluate agreements involving services or products from vendors and contractors; update solution design to address and mitigate changes to existing security policies, standards, guidelines and procedures

Design a Monitoring Strategy for Identity and Security

May include but not limited to: Design for alert notifications; design an alert and metrics strategy; recommend authentication monitors

Design a Data Platform Solution

Design a Data Management Strategy

May include but not limited to: Choose between managed and unmanaged data store; choose between relational and non-relational databases; design data auditing and caching strategies; identify data attributes (e.g., relevancy, structure, frequency, size, durability, etc.); recommend Database Transaction Unit (DTU) sizing; design a data retention policy; design for data availability, consistency, and durability; design a data warehouse strategy

Design a Data Protection Strategy

May include but not limited to: Recommend geographic data storage; design an encryption strategy for data at rest, for data in transmission, and for data in use; design a scalability strategy for data; design secure access to data; design a data loss prevention (DLP) policy

Design and Document Data Flows

May include but not limited to: Identify data flow requirements; create a data flow diagram; design a data flow to meet business requirements; design a data import and export strategy

Design a Monitoring Strategy for the Data Platform

May include but not limited to: Design for alert notifications; design an alert and metrics strategy

Design a Business Continuity Strategy

Design a Site Recovery Strategy

May include but not limited to: Design a recovery solution; design a site recovery replication policy; design for site recovery capacity and for storage replication; design site failover and failback (planned/unplanned); design the site recovery network; recommend recovery objectives (e.g., Azure, on-prem, hybrid, Recovery Time Objective (RTO), Recovery Level Objective (RLO), Recovery Point Objective (RPO)); identify resources that require site recovery; identify supported and unsupported workloads; recommend a geographical distribution strategy

Design for High Availability

May include but not limited to: Design for application redundancy, autoscaling, data center and fault domain redundancy, and network redundancy; identify resources that require high availability; identify storage types for high availability

Design a disaster recovery strategy for individual workloads

May include but not limited to: Design failover/failback scenario(s); document recovery requirements; identify resources that require backup; recommend a geographic availability strategy

Design a Data Archiving Strategy

May include but not limited to: Recommend storage types and methodology for data archiving; identify requirements for data archiving and business compliance requirements for data archiving; identify SLA(s) for data archiving

Design for Deployment, Migration, and Integration (10-15%)

Design Deployments

May include but not limited to: Design a compute, container, data platform, messaging solution, storage, and web app and service deployment strategy

Design Migrations

May include but not limited to: Recommend a migration strategy; design data import/export strategies during migration; determine the appropriate application migration, data transfer, and network connectivity method; determine migration scope, including redundant, related, trivial, and outdated data; determine application and data compatibility

Design an API Integration Strategy

May include but not limited to: Design an API gateway strategy; determine policies for internal and external consumption of APIs; recommend a hosting structure for API management

Design an Infrastructure Strategy

Design a Storage Strategy

May include but not limited to: Design a storage provisioning strategy; design storage access strategy; identify storage requirements; recommend a storage solution and storage management tools

Design a Compute Strategy

May include but not limited to: Design compute provisioning and secure compute strategies; determine appropriate compute technologies (e.g., virtual machines, functions, service fabric, container instances, etc.); design an Azure HPC environment; identify compute requirements; recommend management tools for compute

Design a Networking Strategy

May include but not limited to: Design network provisioning and network security strategies; determine appropriate network connectivity technologies; identify networking requirements; recommend network management tools

Design a Monitoring Strategy for Infrastructure

May include but not limited to: Design for alert notifications; design an alert and metrics strategy