MS-600 Dumps PDF has changed the way candidates do preparation for their certification exam. Qualified specialists have designed this helping study guide get the simplest performance of the applicant. It has reduced students’ efforts now they will easily prepare from to-the-point questions and answers which will be covering all the MS-600 Online Test Engine. You don’t need to find syllabus topics from different places now because all the required information is present at one place at Dumps4Download to ace their exam. Specialists have also developed MS-600 Study Guide that will help to train the students according to the exam. You will even be provided demo inquiries to confirm the standard of the data. We will not charge you for something that's not beneficial for you. So if you'll get failed in your exam, you'll be returned back your money. So if you want to go for Microsoft 365 Certified: Developer Associate and are searching for helping study material then contact us at our site.
Demo Questions:
Question: 1
You need to configure the initial login request in the access token JavaScript script.
Which code segment should you insert at line 01?
A. const scopes = ['https://graph.microsoft.com/.default'];
B. const accessTokenRequest = {
};
C. const scopes = ['https://graph.microsoft.com/Files.Read.All',
'https://graph.microsoft.com/Mail.Send.All'];
D. const accessTokenRequest = {
scopes: ['https://graph.microsoft.com/Files.ReadWrite',
'https://graph.microsoft.com/Mail.Send']
};
Answer: D
Explanation:
Scenario: A Datum identifies the following technical requirements for the planned E-invoicing
capabilities:
• Ensure that all operations performed by E-invoicing against Office 365 are initiated by a user.
Require that the user authorize E-invoicing to access the Office 365 data the first time the application
attempts to
access Office 365 data on the user’s behalf.
Reference:
https://docs.microsoft.com/en-us/graph/permissions-reference
Question: 2
You need to complete the MSAL.js code for SSO.
Which code segment should you insert at line 06?
A. storeAuthStateInCookie: false
B. storeAuthStateInCookie: true
C. cacheLocation: ‘localStorage’
D. cacheLocation: ‘sessionStorage’
Answer: C
Explanation:
Scenario: Implement single sign-on (SSO) and minimize login prompts across browser tabs.
When your application is open in multiple tabs and you first sign in the user on one tab, the user is
also signed in on the other tabs without being prompted. MSAL.js caches the ID token for the user in
the browser localStorage and will sign the user in to the application on the other open tabs.
By default, MSAL.js uses sessionStorage which does not allow the session to be shared between tabs.
To get SSO between tabs, make sure to set the cacheLocation in MSAL.js to localStorage.
Reference:
https://docs.microsoft.com/bs-latn-ba/Azure/active-directory/develop/msal-js-sso
Question: 3
How can you validate that the JSON notification message is sent from the Microsoft Graph service?
A. The ClientState must match the value provided when subscribing.
B. The user_guid must map to a user ID in the Azure AD tenant of the customer.
C. The tenant ID must match the tenant ID of the customer’s Office 365 tenant.
D. The subscription ID must match the Azure subscription used by A Datum.
Answer: A
Explanation:
clientState specifies the value of the clientState property sent by the service in each notification. The
maximum length is 128 characters. The client can check that the notification came from the service
by comparing the value of the clientState property sent with the subscription with the value of the
clientState property received with each notification.
Note: A subscription allows a client app to receive notifications about changes to data in Microsoft
Graph.
Reference:
https://docs.microsoft.com/en-us/graph/api/resources/subscription
Question: 4
Which type of authentication flow should you recommend for the planned integration with Office 365?
A. device code
B. implicit grant
C. authorization code
D. client credentials
Answer: C
Explanation:
To use Microsoft Graph to read and write resources on behalf of a user, your app must get an access
token from the Microsoft identity platform and attach the token to requests that it sends to Microsoft
Graph.
One common flow used by native and mobile apps and also by some Web apps is the OAuth 2.0
authorization code grant flow.
Scenario: Email the generated invoices to customers on behalf of the current signed-in user. Any
emails generated by the system will contain the invoiced.
Use Azure AD to manage identities, authentication, and authorization.
Reference:
https://docs.microsoft.com/en-us/graph/auth-v2-user
Demo Questions:
Question: 1
You need to configure the initial login request in the access token JavaScript script.
Which code segment should you insert at line 01?
A. const scopes = ['https://graph.microsoft.com/.default'];
B. const accessTokenRequest = {
};
C. const scopes = ['https://graph.microsoft.com/Files.Read.All',
'https://graph.microsoft.com/Mail.Send.All'];
D. const accessTokenRequest = {
scopes: ['https://graph.microsoft.com/Files.ReadWrite',
'https://graph.microsoft.com/Mail.Send']
};
Answer: D
Explanation:
Scenario: A Datum identifies the following technical requirements for the planned E-invoicing
capabilities:
• Ensure that all operations performed by E-invoicing against Office 365 are initiated by a user.
Require that the user authorize E-invoicing to access the Office 365 data the first time the application
attempts to
access Office 365 data on the user’s behalf.
Reference:
https://docs.microsoft.com/en-us/graph/permissions-reference
Question: 2
You need to complete the MSAL.js code for SSO.
Which code segment should you insert at line 06?
A. storeAuthStateInCookie: false
B. storeAuthStateInCookie: true
C. cacheLocation: ‘localStorage’
D. cacheLocation: ‘sessionStorage’
Answer: C
Explanation:
Scenario: Implement single sign-on (SSO) and minimize login prompts across browser tabs.
When your application is open in multiple tabs and you first sign in the user on one tab, the user is
also signed in on the other tabs without being prompted. MSAL.js caches the ID token for the user in
the browser localStorage and will sign the user in to the application on the other open tabs.
By default, MSAL.js uses sessionStorage which does not allow the session to be shared between tabs.
To get SSO between tabs, make sure to set the cacheLocation in MSAL.js to localStorage.
Reference:
https://docs.microsoft.com/bs-latn-ba/Azure/active-directory/develop/msal-js-sso
Question: 3
How can you validate that the JSON notification message is sent from the Microsoft Graph service?
A. The ClientState must match the value provided when subscribing.
B. The user_guid must map to a user ID in the Azure AD tenant of the customer.
C. The tenant ID must match the tenant ID of the customer’s Office 365 tenant.
D. The subscription ID must match the Azure subscription used by A Datum.
Answer: A
Explanation:
clientState specifies the value of the clientState property sent by the service in each notification. The
maximum length is 128 characters. The client can check that the notification came from the service
by comparing the value of the clientState property sent with the subscription with the value of the
clientState property received with each notification.
Note: A subscription allows a client app to receive notifications about changes to data in Microsoft
Graph.
Reference:
https://docs.microsoft.com/en-us/graph/api/resources/subscription
Question: 4
Which type of authentication flow should you recommend for the planned integration with Office 365?
A. device code
B. implicit grant
C. authorization code
D. client credentials
Answer: C
Explanation:
To use Microsoft Graph to read and write resources on behalf of a user, your app must get an access
token from the Microsoft identity platform and attach the token to requests that it sends to Microsoft
Graph.
One common flow used by native and mobile apps and also by some Web apps is the OAuth 2.0
authorization code grant flow.
Scenario: Email the generated invoices to customers on behalf of the current signed-in user. Any
emails generated by the system will contain the invoiced.
Use Azure AD to manage identities, authentication, and authorization.
Reference:
https://docs.microsoft.com/en-us/graph/auth-v2-user
